Wouldn't the extra '\r' be swallowed as part of the 'text/xml' value of the Accept: header?
So the \r\n should still terminate that header line. Right? Ed ------------------------------ ✉ Eduard Martinescu <[email protected]> | ✆ (585) 708-9685 | [image: http://www.salsalabs.com] <http://www.salsalabs.com/> - ignite action. fuel change. On Fri, Sep 13, 2013 at 1:08 PM, Baptiste <[email protected]> wrote: > Hi, > > You're right Ghislain. > > Baptiste > Le 13 sept. 2013 18:48, "Ghislain" <[email protected]> a écrit : > > hi, >> >> i am a newbie so don't quote me on this but you show some headers that >> have /R/R/N instead of /r/n >> >> HTTP/1.0 defines the octet sequence CR LF as the end-of-line marker >> for all protocol elements except the Entity-Body (see Appendix B for >> tolerant applications). >> >> >> seems there is a \r that shoudl not be there ? >> 00092 Accept: text/xml\r\r\n >> 00111 Content-Type: text/xml; charset=UTF-8\r\r\n >> >> >> >> best regards, >> Ghislain. >> >
