Ian Holsman wrote: > while I was playing around, I noticed that the Connection Close: header > was being merged, and not set. I'm not 100% on what is needed for > keep-alives, so I left it alone.
Hmmm - I think this should be patched too. Connection: close only makes
sense for the main request, not subrequests...
> the other thing I noticed was that the error message passed back
> could be more informative (like it could pass the error message/#
> received from the proxy). I didn't patch this as I thought it might
> be a security concern (leaking info about hidden boxes) I guess we could
> put the r-proxy'd message in as a notice or something.
In theory the error message would be logged by the backend server (if I
am understanding you correctly) so it shouldn't be necessary to embed
the error message...
Regards,
Graham
--
-----------------------------------------
[EMAIL PROTECTED] "There's a moon
over Bourbon Street
tonight..."
smime.p7s
Description: S/MIME Cryptographic Signature
