I realize this question could go in either the server forums or here based on the responses. Since a SOE would require ArcObjects, I posted here.
For those of you who are working in Server, are you using the proxy page to handle your GET requests that exceed the GET request URL limit or are you developing SOE's to address that kind of special request?
For example, why open your entire REST endpoint to potential abuse (if not securing the web application) for a simple buffer request that may exceed the GET request URL length limitation by deploying the proxy page? One could just as easily move those kinds of requests to the server and let a SOE handle returning a json to the browser for putting up the buffer graphic in the map. No?
For those of you who are working in Server, are you using the proxy page to handle your GET requests that exceed the GET request URL limit or are you developing SOE's to address that kind of special request?
For example, why open your entire REST endpoint to potential abuse (if not securing the web application) for a simple buffer request that may exceed the GET request URL length limitation by deploying the proxy page? One could just as easily move those kinds of requests to the server and let a SOE handle returning a json to the browser for putting up the buffer graphic in the map. No?