On 25/07/07, Daniel JavaDev <dan.javadev@xxxxxxxxxxxxxx> wrote:
Hi all, I have the following rules on my apache 2.2.4 config: RewriteEngine on RewriteRule ^/someURL http://anotherURL [P] where someURL is the a publicly available url, and anotherURL is a private url (localhost on another port). This setup is for restricting access to an application server. It all works fine, except that the application needs to return an empty body response (ACK) for some HTTP POSTs, and apache is adding the CONTENT-LENGTH: 0 header to those responses, which is an invalid header in the context of the protocol used by the application. Is there anyway of forcing apache not to add the content-length header to the responses?
Apache is a http server, not a http-but-not-really server. If your client barfs on a correct Content-Length header then your client is broken. I'd suggest either using 204 No Content, or designing your own protocol. -- noodl --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|