Hello Again,
I've just discovered that, in the request line of the HTTP message, I have 
it as:
POST /test/testpage.asp\r\nHTTP/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.
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?

Thanks,
Kalyan

"Kalyan Sakhamuri" <[EMAIL PROTECTED]> wrote in message 
news:[EMAIL PROTECTED]
> Hello All,
> We have an application which makes a few requests to certain webservices 
> over the HTTP.  In order to emulate the HTTP using NetLib, we added a few 
> headers to the standard TCP protocol and were successfully able to get 
> this resolved and it was working fine with all the devices that had some 
> kind of wireless capability.  However, on the Treo 600 - when we tried to 
> do the same, it works fine on the GSM technology, but when it comes to the 
> Sprint or the Verizon services, it fails.  At first we thought, it is 
> because Sprint and Verizon use CDMA against GSM.  However, after further 
> tests, we figured that we were getting a HTTP/1.1 400 Bad Request (error) 
> (with
> server: Proxy/1.1).  So, I guess, it is related to the Proxy Server used 
> by these service providers.
>
> What I'm trying to figure out now is, how to come up with a standard, that 
> would work with all the service providers, where I don't have to do 
> special customizations for the service providers, as I'm not sure, how to 
> figure out
> the service provider in the first place.  I'ld greatly appreciate any help 
> in this regard.
> Thanks,
>
> -- 
> Kalyan Sakhamuri
> Networking Technology, Inc.
> 637 Tebbston Drive
> Pasadena, MD 21122
> Ph: (410) 255-7600 (x 11)
>
> 



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

Reply via email to