The Freak Parade - Latest Comments in Simple ASP.NET MVC Ajax Proxy

Re: Simple ASP.NET MVC Ajax Proxy

Hal Lesesne — Sun, 26 Jun 2011 15:56:13 -0000

How about handling POST/PUT scenarios?

Re: Simple ASP.NET MVC Ajax Proxy

Chris Hill — Wed, 10 Mar 2010 04:34:35 -0000

Worked great thanks. Just one slight typo in the code, line 40 in the first code snippet has got a space between the < and = on the if statement.

Re: Simple ASP.NET MVC Ajax Proxy

chris — Thu, 10 Sep 2009 18:13:45 -0000

I did some research after reading your post. You are correct. The resource on the other end of the XSS call needs to be aware of the JSONP arrangement. It must "pad" the response with the call to the callback function. Rick Strahl has a good write up on the subject.

http://www.west-wind.com/We...

Re: Simple ASP.NET MVC Ajax Proxy

nstults — Thu, 10 Sep 2009 18:04:08 -0000

My understanding of JSONP is that the script that wants to access remote data (which is expected to be javascript, I presume, whereas in this example the payload is a binary (png) stream) needs to be aware of the JSONP arrangement, whereas in this case the goal is allow a third party component (OpenLayers) interact with a map server on a different domain without having to write and specific client side or server side glue code to make it happen, we can just give the OpenLayers control a url to a WMS server and everything works as expected. Also with JSONP (as I understand it) the cross-domain resource needs to be aware of the protocol, whereas with a proxy, the cross-domain resource does not need any modification whatsoever. But I only briefly looked at JSONP at your mention, so I have a very light understanding of its capabilities.

Re: Simple ASP.NET MVC Ajax Proxy

chris patterson — Thu, 10 Sep 2009 16:37:02 -0000

Nice.

When does a method like this need to be implemented versus taking advantage of something like JSONP?