Re: HTTP problem, wrong characters sent (HTTP pro's needed!)
- From: "webEater" <andreaskalsch@xxxxxx>
- Date: 27 Sep 2006 12:57:29 -0700
Hi,
thank you, your notes helped me very much!
You haven't implemented HTTP/1.1 Content-transfer-encoding: chunked, which is
mandatory and very commonly used in HTTP/1.1 server replies.
http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.6.1
"All HTTP/1.1 applications MUST be able to receive and decode the "chunked"
transfer-coding, and MUST ignore chunk-extension extensions they do not
understand."
Some choices:
(1) Make HTTP 1.0 requests instead of 1.1.
(2) Implement chunked transfer-coding.
(3) Use an HTTP client library that understands it, for example cURL.
I took the first choice - taking v1.0 - it's simpler. Now it works
properly ,)
.
- References:
- HTTP problem, wrong characters sent (HTTP pro's needed!)
- From: webEater
- Re: HTTP problem, wrong characters sent (HTTP pro's needed!)
- From: Andy Hassall
- HTTP problem, wrong characters sent (HTTP pro's needed!)
- Prev by Date: Re: Retrieving the multiple values set by a form
- Next by Date: Re: mbstring extension not found; how to find it?
- Previous by thread: Re: HTTP problem, wrong characters sent (HTTP pro's needed!)
- Next by thread: Re: HTTP problem, wrong characters sent (HTTP pro's needed!)
- Index(es):
Relevant Pages
|