Robert Segall wrote:
On Thu, 2008-07-03 at 09:21 -0200, Thomas M Steenholdt wrote:
Hi there...
I'm trying to use Pound for most of my companys public webservers. Both
as a security measure and as a way to save public IP addresses while
adding a load of flexibility. And pound seems to be working perfectly
for all of this.
But I recently discovered that our Outlook WebAccess, uses at least one
HTTP verb (BPROPFIND) that do not seem to be accepted/handled by Pound.
Is there a reason why Pound does not attempt to handle this verb or
could support for this be easily added?
Is there any way to make pound not filter the verbs at all (perhaps only
warn of bad requests) when prod-sites run into problems like this?
Thanks in advance :-)
Thanks Thomas, this is a simple oversight. The patch will appear in the
next release. In the meantime you can easily modify it yourself - edit
config.c and add BPROPFIND into the last regex in the xhttp array.
Hi Robert...
Looking in config.c, it appears that BPROPFIND should probably be in
both xHTTP regex 3 and 4, right? The other of the B-family verbs
(BPROPPATCH,BMOVE,BCOPY etc.) are included, starting from xHTTP 3.