First, please don't top post. Second, please don't quote an entire
digest message when making a reply. Third, please don't reply to a
message when starting a new topic--it messes up the threading.
Please read the Etiquette link at the bottom of each message:
http://curl.haxx.se/mail/etiquette.html

On Fri, Mar 02, 2012 at 11:52:00AM +0800, hui wrote:
> The server used by many routers as multicast to http proxy, and
> http response header line end with "\n".In this case,CURL can't
> understand the server response. But if http response header line end
> with "\r\n",CURL can work!
>
> What can I do?

If the server is broken, then it needs to be fixed. The HTTP spec is
quite clear on how headers from servers should look. curl has been
deployed for years with great success, so the number of servers broken
in this way is evidently not very great.

If you have a special case that you're trying to work around, and when
you talk about multicast it sounds like you're not talking about
standard HTTP at all, then you're free to change the curl source to get
around this issue in your own application.

>>> Dan
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2012-03-02