How to understand why FallbackRoute doesn't work

sviluppo1 · June 14, 2018, 9:19am

I’ve added a Service, that has 1 Any() method, that uses a DTO with FallbackRoute attribute.

public class HomeService : AppService
{
    public object Any(Fallback fallback)
    {
        // do things
    }
}

[FallbackRoute("/{Path*}")]
public class Fallback
{
    public string Path { get; set; }
}

I have 2 issues:

I can’t get any call to get to my method (it just gives me 404)
If I try to get to http://localhost/ I get a 302 to the /metadata page.

Can you help me understand why this happens, and\or how I can investigate this issue?
Thanks

mythz · June 14, 2018, 9:58am

All SPA templates have the same fallback path in all hosts:

github.com

NetCoreTemplates/vue-spa/blob/master/MyApp.ServiceInterface/MyServices.cs#L12


using System.Collections.Generic;
using System.Linq;
using ServiceStack;
using ServiceStack.Script;
using ServiceStack.DataAnnotations;
using MyApp.ServiceModel;


namespace MyApp.ServiceInterface
{
    [Exclude(Feature.Metadata)]
    [FallbackRoute("/{PathInfo*}", Matches="AcceptsHtml")]
    public class FallbackForClientRoutes
    {
        public string PathInfo { get; set; }
    }


    public class MyServices : Service
    {
        //Return index.html for unmatched requests so routing is handled on client
        public object Any(FallbackForClientRoutes request) => Request.GetPageResult("/");

There must be something else causing the conflict, like all things look at the raw HTTP Headers to see if they provide any insight on what’s causing it.

sviluppo1 · June 14, 2018, 10:04am

I’m sorry, our GetRouteAttributes override was modifying the fallback path.