question about http referer and server.response.code

I need a solution

We have employees who use an application which will display a map when the map button is clicked. This has stopped working. I ran a trace and what I see is a server.response.code of 400 and a client response.code of 400. Does that mean the proxy got a 400 from the server it was trying to go to (in this case arcgis.com)?

When I look at what is being sent there is a malformed url but it is in the http referer part of the header, would this still affect it?  I see other times when they go to the site and if there is no referer they get a 400/400. 

This is snippets of the trace… (note the “//” in the referer line which make it malformed)

Code 200/200 with no referer…

GET http://js.arcgis.com/3.15/esri/dijit/BasemapGallery.js
  DNS lookup was unrestricted
origin server next-hop IP address=13.32.80.95
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko
user: unauthenticated
authentication status=’not_attempted’ authorization status=’not_attempted’
  url.category: COT_Services@Policy;COT_Whitelist@Policy;Technology/Internet@Blue Coat
    total categorization time: 1
    static categorization time: 1
server.response.code: 200
client.response.code: 200

Similar url but with referer and now code 400/400

GET http://js.arcgis.com/3.15/esri/nls/jsapi_en-us.js
  DNS lookup was unrestricted
origin server next-hop IP address=13.32.80.95
Referer: http://tpdrms80:1911/rms/web_components//arcGIS/arcGIS.html
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64) AppleWebKit/538.1 (KHTML, like Gecko) Genero Desktop Client Safari/538.1
user: unauthenticated
authentication status=’not_attempted’ authorization status=’not_attempted’
  url.category: COT_Services@Policy;COT_Whitelist@Policy;Technology/Internet@Blue Coat
    total categorization time: 14
    static categorization time: 14
server.response.code: 400
client.response.code: 400

Also, this is the second time since the categorization was changed a week or so ago that we have had this issue, the other site was online811, which also had the double // in certain urls in their site. The proxy response was malformed request, and if I removed one of the “/” the url would work. We have been using both of the sites forever, and the vendors say they made no changes.

Any assistance is greatly appreciated. We have ProxySG 900-10B with 6.6.5.17

0

Related:

  • No Related Posts

Leave a Reply