By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,988 Members | 1,049 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,988 IT Pros & Developers. It's quick & easy.

Disallow "HTTP chunked" transfer !

P: n/a
Hi !

Yesterday, I posted a topic regarding to XML problem that I've been
having. The old topic can be found at:
http://groups.google.com/group/comp....0eeb03626018f4

Thanks to Álvaro G. Vicario for pointing out "chunked" transfer thing.
Anyway, I tried to avoid "chunked" transfer in HTTP protocol. I have
looked at "transfer-encoding" on the web, but it doesn't help much.
What value/variable should I specify in HTTP request to ask the server
not using "chunked" transfer ?

If anyone experienced this problem/ know how to do this, please share
your thought. Any help would be greatly appreciated.

Thanks,

Lazy Pig (Josh)

Jun 22 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a
On 22 Jun 2006 09:53:17 -0700, "la*******@gmail.com" <la*******@gmail.com>
wrote:
Yesterday, I posted a topic regarding to XML problem that I've been
having. The old topic can be found at:
http://groups.google.com/group/comp....0eeb03626018f4

Thanks to Álvaro G. Vicario for pointing out "chunked" transfer thing.
Anyway, I tried to avoid "chunked" transfer in HTTP protocol. I have
looked at "transfer-encoding" on the web, but it doesn't help much.
What value/variable should I specify in HTTP request to ask the server
not using "chunked" transfer ?

If anyone experienced this problem/ know how to do this, please share
your thought. Any help would be greatly appreciated.


HTTP/1.1 clients _must_ be able to accept and decode chunked transfer
encoding. If you are making an HTTP/1.1 request to fetch the data, then its a
bug in your code if you do not handle it. Are you doing raw requests using
fsockopen() etc.?

Some options:

(1) Implement chunked transfer encoding decoding.
(2) Use a library that implements this for you, rather than rolling your own
HTTP client (e.g. cURL, or PHP fopen wrappers).
(3) Make HTTP/1.0 requests instead.

--
Andy Hassall :: an**@andyh.co.uk :: http://www.andyh.co.uk
http://www.andyhsoftware.co.uk/space :: disk and FTP usage analysis tool
Jun 22 '06 #2

P: n/a
Hi Andy,

Thanks a lot for your response. My code works when I use HTTP 1.0 Raw
request with fsockopen.

Lazy Pig

Andy Hassall wrote:
On 22 Jun 2006 09:53:17 -0700, "la*******@gmail.com" <la*******@gmail.com>
wrote:
Yesterday, I posted a topic regarding to XML problem that I've been
having. The old topic can be found at:
http://groups.google.com/group/comp....0eeb03626018f4

Thanks to Álvaro G. Vicario for pointing out "chunked" transfer thing.
Anyway, I tried to avoid "chunked" transfer in HTTP protocol. I have
looked at "transfer-encoding" on the web, but it doesn't help much.
What value/variable should I specify in HTTP request to ask the server
not using "chunked" transfer ?

If anyone experienced this problem/ know how to do this, please share
your thought. Any help would be greatly appreciated.


HTTP/1.1 clients _must_ be able to accept and decode chunked transfer
encoding. If you are making an HTTP/1.1 request to fetch the data, then its a
bug in your code if you do not handle it. Are you doing raw requests using
fsockopen() etc.?

Some options:

(1) Implement chunked transfer encoding decoding.
(2) Use a library that implements this for you, rather than rolling your own
HTTP client (e.g. cURL, or PHP fopen wrappers).
(3) Make HTTP/1.0 requests instead.

--
Andy Hassall :: an**@andyh.co.uk :: http://www.andyh.co.uk
http://www.andyhsoftware.co.uk/space :: disk and FTP usage analysis tool


Jun 22 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.