HTTP SMSC Connection.

HTTP SMSC Connection. SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through October 31, 2007 » HTTP SMSC Connection. « Previous || Next »
Author Message
Frank Grygus
New member
Username: Fgrygus

Post Number: 7
Registered: 08-2007
Posted on Wednesday, September 19, 2007 - 04:49 pm:   

Bryce,

Can I control the UserAgent(browser) field when the gateway attempts a HTTP SMSC connection?

Frank
Frank Grygus
New member
Username: Fgrygus

Post Number: 8
Registered: 08-2007
Posted on Thursday, September 20, 2007 - 01:27 pm:   

Good morning Bryce,

I am trying to setup a HTTP SMSC connection from one NowSMS gw behind a http proxy to another NowSMS gw that is not. The NowSMS gw behind the http proxy is failing to make the connection through the proxy. The commercial proxy is failing the connection with "400 Bad request [code=BAD_REQUEST_NO_HOST]".

I have consulted with my IT department on the failure, and they indicated that my application(NowSMS) is not following http/1.1 spec. It is missing the Host header field. They provided me a working example using curl.

Now, for sake of arguement, I tried the NowSMS gw connection through a SQUID Proxy in my lab and it worked. So I suspect that the comercial proxy being used is requiring the clients (NowSMS) to follow all http specs to the letter.

How do I add the header field in the outgoing HTTP GET to be http/1.1(rfc 2616) complient?
Malcolm - Now Support
Moderator
Username: Malcolm

Post Number: 221
Registered: 12-2006
Posted on Thursday, October 18, 2007 - 08:21 pm:   

Just a follow-up ... as I think Bryce responded to this directly.

Indeed, there was an issue, and the following change was implemented in an update:

* When making HTTP requests via an HTTP proxy server, include a "Host:" header. Previously, the "Host:" header was only included when not using an HTTP proxy. (The old approach was valid for HTTP/1.0, but not valid for HTTP/1.1.) This logic only applies to HTTP SMSC connections via an HTTP Proxy, and to User Agent Profile (UAProf) retrieval via an HTTP Proxy. MMS retrieval over MM1 via an HTTP proxy already included all required headers.

Login Login / Register Logout Logout Search Last 30 Days Topics Topics