(This message has been automatically imported from the retired mailing list)
hey, i think i already out of topic i think this is the problem from the
sender not the zato, so i think we better stop the conversation, im so sorry
On Thu, Feb 5, 2015 at 3:35 PM, Dariusz Suchojad firstname.lastname@example.org wrote:
Here it is in server1log.log file:
line 191, in on_wsgi_request
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 …
… whereas Zato assumes it will be always provided.
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)