Select to view content in your preferred language

3.9 Internal Server Error 500

6308
22
05-14-2014 05:27 AM
BrianCowan
New Contributor
I downloaded ArcGIS 3.9 but after updating the files and running my map I got the following error

GET http://localhost:9000/proxy?./proxy?http://services.arcgisonline.com/ArcGIS/rest/services/World_Stre...   500 (Internal Server Error)

Any help would be greatly appreciated!
0 Kudos
22 Replies
Noah-Sager
Esri Regular Contributor
Hi ClevelandFan,

Welcome to Esri Forums! Thank you for posting your question here.

From the error message in the picture you uploaded, it looks like the error is related to the proxy. Have you download and configured the proxy to work with your application? I would start here. Also, there are good instructions in the ReadMe file on GitHub.

Using the proxy
https://developers.arcgis.com/javascript/jshelp/ags_proxy.html

Hope this helps!

-Noah
0 Kudos
BrianCowan
New Contributor
Thank you for your response Noah!

I had everything working fine with 3.8 but upgrading to 3.9 caused that to crash after downloading it, changing the files, and updating the database. From what I could tell it had to do with it trying to access the proxy twice in the GET call GET http://localhost:9000/proxy?./proxy......from init.js, but I never had that problem with 3.8. Is there a separate download needed for it to work with the existing project?

Thank you
0 Kudos
Noah-Sager
Esri Regular Contributor
As far as I know, there isn't a separate download needed for this sort of workflow. I haven't locally hosted version 3.9 yet, so I'll give that a shot and see if I can reproduce the error.

Are you using our proxy? If so, which proxy are you using, DotNet, Java, or PHP?

Can you recreate the error in a simplified sample application?
0 Kudos
JeffPace
MVP Alum
Thank you for your response Noah!

I had everything working fine with 3.8 but upgrading to 3.9 caused that to crash after downloading it, changing the files, and updating the database. From what I could tell it had to do with it trying to access the proxy twice in the GET call GET http://localhost:9000/proxy?./proxy......from init.js, but I never had that problem with 3.8. Is there a separate download needed for it to work with the existing project?

Thank you


The API doesnt have a database, so I am also confused about your comment.  If you are doing a local install, does the sample page work?

Based on the link you posted it looks like you have a pathing error in your map
0 Kudos
BrianCowan
New Contributor
After some tweaking I was able to load the map but I now receive a 403 Forbidden error. It appears esri.config.defaults.io.proxyUrl is placing ./proxy twice.

http://localhost:9000/proxy?/proxy?http://services.arcgisonline.com/ArcGIS/rest/services/World_Street_Map/MapServer/tilemap/10/408/272/...
0 Kudos
JohnGravois
Frequent Contributor
brian,
can you share the line of code where you set the location of your proxy and explain where it actually sits with respect to your application?

also, since your proxy is throwing a 403, are you sure that the resource which is being requested is specified in your proxy.config whitelist?
TamaraOsborn
New Contributor

I am having exactly the same problem where the proxy appears twice in the request URL. This is also specific to tilemap like Brian's problem.

I am using the latest JSP proxy from github, ver 1.0. I have not modified the proxy at all. My proxy.config has the following in it:

    <serverUrl url="http://services.arcgisonline.com"

        matchAll="true"/>

My other calls are fine, it is just a couple for tilemap that are failing because of the invalid url format.

If you fixed it, how did you do it?

0 Kudos
MatthewLofgren
Occasional Contributor

I had this problem too. I came across a post, that I can't seem to find now, that said to use an absolute path rather than relative path because of some bug.

So, something like this:

esriConfig.defaults.io.proxyUrl = "http://yourServer/proxy.ashx"; //Full path required due to some bug....

0 Kudos
TamaraOsborn
New Contributor

Thanks for the suggestion. Hardcoding the path ( esri.config.defaults.io.proxyUrl = "http://localhost:8080/proto1/proxy/proxy.jsp";) didn't fix the problem. The same thing happens where the proxy appears twice in the request URL - see below.

http://localhost:8080/proto1/proxy/proxy.jsp?http://localhost:8080/proto1/proxy/proxy.jsp?http://ser...

0 Kudos