You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Marten Lehmann <le...@cnm.de> on 2004/08/02 21:52:20 UTC
Re: [users@httpd] more output than send by the script?
Hello,
once again.
I was successful with disabling chunked encoding with
BrowserMatch .* force-response-1.0 downgrade-1.0 nokeepalive
However, I'm not very happy with this. Especially, because maybe I'll
move from Apache to Tomcat for this application later and there might be
no chance to force the same behavior. Also, I don't like to use HTTP/1.0
with the Host header, because AFAIK the host-header _may_ work with
HTTP/1.0, but not every http-server is required to support this. My
problem is, that I have to build a simple http-client for perl and php.
And since it shall be available within a certain toolkit for a wide
range of users, I can't rely on any modules in perl or PHP-PEAR. To
disable keep-alive connections, I can send a
Connection: close
header. But what do I have to send to inform the webserver, that I can't
handle chunked encoding?
Accept-Encoding: none
doesn't work.
Accept-Encoding: plain
doesn't work either. I'm not that familar with http and I couldn't find
the information in the RFCs.
Regards
Marten
---------------------------------------------------------------------
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@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] more output than send by the script?
Posted by Joshua Slive <js...@gmail.com>.
On Mon, 02 Aug 2004 21:52:20 +0200, Marten Lehmann <le...@cnm.de> wrote:
> Hello,
>
> once again.
>
> I was successful with disabling chunked encoding with
>
> BrowserMatch .* force-response-1.0 downgrade-1.0 nokeepalive
>
> However, I'm not very happy with this. Especially, because maybe I'll
> move from Apache to Tomcat for this application later and there might be
> no chance to force the same behavior. Also, I don't like to use HTTP/1.0
> with the Host header, because AFAIK the host-header _may_ work with
> HTTP/1.0, but not every http-server is required to support this.
Whew. You're stubborn about that one. In the real world, ALL servers
will handle the Host header on HTTP/1.0 requests. Until recently, a
very large portion of web browsers only supported HTTP/1.0, but all of
these browsers used the Host header because many sites are
innaccesible without it.
As far as I know, there is no way for an HTTP/1.1 client to request no
chunking. (But I'm not a protocol expert, so I may be wrong.) But
again, if you want to make requests using HTTP, you should really
bite-the-bullet and use a proper client library, regardless of the
extra complication.
Joshua.
---------------------------------------------------------------------
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@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org