Yes, that's exactly what the RFC also states.  However, I tried to route a 
post method from the IE6.0 to a TCP server, I'm hosting here and when I saw 
the message format, it had a CRLF after the URI.  That was the first 
confusion.  Then secondly, with certain devices reporting a HTTP/1.1 400 Bad 
Request, if I use a space instead of the CRLF has added to it.  Any idea why 
such things are happening?
Thanks
Kalyan

"Simon Dick" <[EMAIL PROTECTED]> wrote in message 
news:[EMAIL PROTECTED]
>
> Palm Developer Forum wrote on 15/9/04 21:14
>>Hello Again,
>>I've just discovered that, in
>>the request line of the HTTP
>>message, I have
>>it as:
>>POST
>>/test/testpage.asp\r\nHTT
>>P/1.1\r\n (followed by the
>>headers)
>>
>>However, I came across some
>>posting yesterday, in which
>>it says that after
>>the file (or resource) name,
>>there should be a space (and
>>not a CRLF) before
>>the HTTP (and version).
>>Confirmed this with the RFC
>>which says:
>>
>>        Request       = Request-
>>Line              ; Section 5.1
>>                        *(( general-
>>header        ; Section 4.5
>>                         | request-header
>>; Section 5.3
>>                         | entity-header )
>>CRLF)  ; Section 7.1
>>                        CRLF
>>                        [ message-body ]
>>; Section 4.3
>>
>>        Request-Line   = Method
>>SP Request-URI SP HTTP-
>>Version CRLF
>>
>>So, changed it and seemed to
>>have fixed the problem with
>>the Sprint service.
>>However, now the rest of the
>>devices stopped working.
>>Then changed it back
>>to the way it was and back to
>>where I started.  All the other
>>devices would
>>work but the Sprint Treo 600
>>fails.
>>
>>Can any one confirm,
>>whether it should be a space
>>or a CRLF between the URI
>>and the HTTP.
> It should definitely be a space followed by the HTTP part\r\n then headers 
> followed by an empty \r\n terminated line (that's what I believe you're 
> missing)
>>Also, may be, one of the Net
>>Gurus can explain why it
>>would work with
>>certain devices in the way
>>described in the RFC and not
>>with the rest?
> If you don't use a space there then the web server/proxy will treat it as 
> a HTTP 0.9 request and not require the blank line.
> Hope that is some help!
>
> 



-- 
For information on using the Palm Developer Forums, or to unsubscribe, please see 
http://www.palmos.com/dev/support/forums/

Reply via email to