(Migrated) [Rafed Ramzi] [Rafed Ramzi] ASK::Failed To send http request to zato

Community support
#1

(This message has been automatically imported from the retired mailing list)

Yes you right! it solved my problem at localhost

but when i send the request from my shared-hosting the request didn’t reach
the server but it did when request to http://server.projectsuroto.com/ not
to http://server.projectsuroto.com:11223/test

Thank You,

On Thu, Feb 5, 2015 at 3:35 PM, Dariusz Suchojad dsuch@zato.io wrote:

Here it is in server1log.log file:

File “/opt/zato/2.0.0/zato-server/src/zato/server/base/parallel.py”,
line 191, in on_wsgi_request
’user_agent’: wsgi_environ[‘HTTP_USER_AGENT’],
KeyError: u’HTTP_USER_AGENT’

The application you are using doesn’t send the User-Agent HTTP header.

I’ve never heard of any such application before but yes, it turns out
that User-Agent is optional …

https://tools.ietf.org/html/rfc2616#section-14.43

… whereas Zato assumes it will be always provided.

What next:

  • When using http://requestmaker.com/ please add the User-Agent header
    with any value, even ‘123’ will do.

  • Zato will be updated so it doesn’t assume User-Agent is always
    available. The change will be released in 2.0.2 (we are at 2.0.1 now)

#2

On 05/02/15 10:23, Rafed Ramzi wrote:

but when i send the request from my shared-hosting the request didn’t
reach the server but it did when request
to http://server.projectsuroto.com/ not
to http://server.projectsuroto.com:11223/test

I’m not sure what it means the requests didn’t reach it?

I cannot connect to http://server.projectsuroto.com:11223/test just fine
from around the world and I can see the response of:

["[“response”]"]

How do you mean it didn’t reach it?

thanks,

#3

On 05/02/15 10:27, Dariusz Suchojad wrote:

I cannot connect to http://server.projectsuroto.com:11223/test just fine

Sorry - obviously I meant ‘I can connect to’ instead of ‘I cannot’.