> On 6 Apr 2016, at 11:30 AM, Jesus Cea <[email protected]> wrote: > > I think that current MOD_WSGI can only implement HEAD, GET, PUT methods, > but CAN NOT implement OPTIONS or PROPFIND. At least, I am not able to > get my code called when my client invoke those HTTP verbs. > > Am I in an error?.
It will handle anything it is given. The issue is whether you have installed any other Apache modules that swallow up those types of requests. If you are for example running WebDav in an overlapping URL namespace, it is possible it might swallow them up. I am not familiar with WebDav, but have seen others talk about issues with something like that in the past. If I use mod_wsgi-express to host a test application that just mirrors back the request environment, both work fine. $ curl -X OPTIONS http://localhost:8000 | grep REQUEST_METHOD % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 7632 0 7632 0 0 1068k 0 --:--:-- --:--:-- --:--:-- 1242k REQUEST_METHOD: ‘OPTIONS' $ curl -X PROPFIND http://localhost:8000 | grep REQUEST_METHOD % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 7646 0 7646 0 0 1158k 0 --:--:-- --:--:-- --:--:-- 1244k REQUEST_METHOD: ‘PROPFIND' So they do get through. > (See my message to the mailing list sent the 3th of December). I don’t know what message you are talking about. You would need to find it in the Google Groups archive and provide a link. Graham -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
