I don't really think this is even for this forum or this site. But I really have no idea where to go on this so even if no one can answer it on here could you maybe point me to a site where I could figure this out?
I'm a developer. We program a front-end GUI using AIR and a back-end using java. The java service listens on port 1813 for our requests from the GUI and then sends those requests off to a gateway server which returns the data to display.
For some reason, it works just fine in one scenario, but in another it doesn't. Keep in mind this used to work and I have no idea what changed. If I run my application, it starts up our java service. We then start sending requests to http://localhost:1813 form the GUI to the java service. When the application runs and sends these requests, I'm getting 502 errors. If I run the application and use POSTMAN to send the exact same request, I get a correct response.
The request is xml and I have set the headers to application/xml. The method for both is POST. The only difference I can really see in the headers in Fiddler is that in the Transport section the one that works using POSTMAN has "Connection: Keep-Alive" and the failed one from within the application has "Proxy-Connection: Keep-Alive". But I don't know enough to know if that matters or what it means or why it would say that.
I have attached a failed and successful image to show the headers in fiddler.
Thanks for any help.
1 Answer, 1 is accepted
Rank 1
I found this article on stackoverflow
http://stackoverflow.com/questions/18451057/sending-connection-header-set-as-keep-alive
And I actually noticed that when a request is successful, if I click the session to inspect it before i get a response I will see "Proxy-Connection" and then when it's successful it renames it to "connection". When it works, it's renamed, when it doesn't, it's not.