> On 2016-06-13 13:20, Roberto De Ioris wrote: > >> Hi, the 'notfound' plugin raises a 404 automatically, so you can use it >> as >> the default plugin without adding routing rules. > > Perhaps, I misunderstand something, but simply loading notfound plugins > changes > nothing - I still get 500 error. > > When I run (2.0.13.1): > > $ uwsgi --http :8888 --http-modifier1=5 --static-map /s=. --plugin > notfound --manage-script-name --mount /a=uwsgi-test.pl > > and when accessing http://127.0.0.1/s/not-exists it produces this: > > --- unable to find perl application --- > [pid: 11812|app: -1|req: -1/4] 127.0.0.1 () {28 vars in 319 bytes} [Mon > Jun 13 18:43:11 2016] GET /s/not-exists => generated 21 bytes in 0 msecs > (HTTP/1.1 500) 2 headers in 83 bytes (0 switches on core 0) > > When accessing existing file, everyting is fine, and when accessing > /a/something > it is forwarded to the application (as expected). > >
notfound is useful only when you do not have other request plugin active. In all the other case the request not managed by the static file handler is passed to the final plugin. You need to find a way to selectively choose when a non-existent resource should trigger the notfound plugin and when the psgi plugin. Something like: route = ^/static setmodifier1:0 route = ^/foo setmodifier1:5 -- Roberto De Ioris http://unbit.com _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
