> 2013/3/10 Guido Berhoerster <[email protected]> > >> Does that idea make any sense? If not, I don't think >> --static-allowed-method would be bad, it's just one additional >> setting users need to be aware of. > > > IMHO this should be transparently handled at the plugin level, not > globally. I think that global setting might not work if someone load cgi > and php app into single uWSGI instance using config magic and internal > routing. >
I think the general rules should be: 1) if there is a static check (whatever form) static indexes must be honoured 2) if a static index is found it has precedence and it is moved to file serving mode 3) before sending the file, the request method is checked for GET/HEAD, other methods are passed to the plugin (or the internal routing) The question is: are there any case in which serving a static file with "POST" (for example) is needed ? If yes, the --static-allowed-method is a need -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
