proxy page - how can I tell the length of the URL?

I'm an ArcGIS Server Javascript API application that uses the buffer operation to buffer a point by 35m and finds features within that distance. The javascript API documentation recommends using a proxy page if doing buffer operations but then in the part in the javascript API documentation that explains the proxy page it says ???Common scenarios where you may run into URL length issues are when you use the buffer from a complex polygon as the input to a query task???. If I???m only buffering a point then would that run the risk of running into URL length issues? What is the URL that would be potentially long? And how can I test the length of the URL being created?

In fact you can easily get into this scenario if you, for example, are bufferizing a irregular polygon with many vertices and inner holes. This kind of geometry needs to be serialized according to the rest specification. Polygons contains rings and rings contains points. If you have many rings and points, you'll see this kind of problem in action.

Even though you are buffering a point, the resultant buffer is a polygon. You will have a large number of coordinates from that process, so no matter what you are buffering, you'll have to set up the proxy.

Even though you are buffering a point, the resultant buffer is a polygon. You will have a large number of coordinates from that process, so no matter what you are buffering, you'll have to set up the proxy.

In that case, the serialized buffer is sent through the response body, right?

I think that Mike is trying to understand how to deal with the GET/POST verb on the request, because of the limitations on the size of a querystring when using GET requests. Let me know if I got something wrong.

Thanks for your replies. I've got one or two more questions. The maps that will perform the buffer have to be accessed via https without any certificate warnings. How can I be sure the proxy is working correctly? I've followed the instructions on github but when I go check the proxy is able to forward request directly in the browser I get a 403 error message saying access is denied:

I ran into this exact same issue, so I opened an incident with ESRI. The answer is to provide the full URL to your specific proxy page that would go something like: http://"Server Name"/Proxy/proxy.ashx

The url assumes you put the proxy files into a folder called Proxy on your IIS server at c:\inetpub\wwwroot.

This is where I feel ESRI's documentation is lacking as they use a shorthand path of "/proxy" because of how they set their own IIS server up.

I have another question though - how can I test that the proxy is working in my javascript application? In my javascript application the buffer operation was completing successfully before I put in the proxy reference. If I look in the developer tools at the network requests it says:

I'm coming back to this because I never got it sorted before. I've got the reference to the proxy in my code. If I don't include the line

esriConfig.defaults.io.alwaysUseProxy = true;

then the buffer operation executes using GET.

If I include the flag to set alwaysUseProxy to be true I can see that the requests for loading my ArcGISTiledMapServiceLayer tiles are going through the proxy, however the buffer operation doesn't execute (the buffer doesn't appear in the network requests and there aren't any errors in the console). Any suggestions how I can work out what's going on?