Service CORS and Route Attributes

Question

I have the CORS feature enabled. I'm finding that if I don't have:

[Route("/cors_endpoint", "GET, OPTIONS")]

on my request dto, then I get a 404.

As I'm using the CorsFeature, and the PreRequestFilter below, I don't understand where this 404 is coming. (I also have authentication attributes in play, but am doing stateless auth with it).

Plugins.Add(new CorsFeature());
PreRequestFilters.Add((req, res) => {
    if (req.Method == "OPTIONS")
    {
         res.StatusCode = 200; //my hack
         res.EndRequest();
    }
});

Any ideas? PS. Still on 3.9.x

Edit: My real questions maybe should be:

[Route("/cors_endpoint", "GET")]

This gives a 404, and doesn't hit the PreRequestFilter at all. Why?

score 2 · Answer 1 · answered Mar 11 '14 at 19:54

2

The "new API" changes introduced more HTTP verb signatures. Try adding the the service Options method.

public class ReqstarsService : Service
{
    [EnableCors]
    public void Options(Reqstar request) {}
}

answered Mar 11 '14 at 19:54

kampsj

3,139
5
34
56

I like this - usually i make an empty Options() method. Remove the 'hack' on PreRequestFilters and let the Options() method return. – Raul Nohea Goodness Mar 11 '14 at 23:17
This means adding something to every service, which I would rather avoid – Chris Mar 12 '14 at 09:26
And actually, it is unnecessary.... As long as I have the "OPTIONS" in my route attribute it works. – Chris Mar 12 '14 at 10:10

Service CORS and Route Attributes

1 Answers1