One of the pain points with developing AJAX, JavaScript, JQuery, and other client-side behaviors is that JavaScript doesn’t allow for cross domain request for pulling content. For example, JavaScript code on could not pull content or data from

One way to overcome this issue is by using a server-side proxy on the site running the JavaScript code. There is already are well documented PHP solutions on the web, however I couldn’t find very many .NET-based solutions. This simple C# code takes the URL passed to it through the URL encoded query string, retrieves the content of the URL and outputs it as if it were content on the site.


using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Net;
using System.IO;

namespace Proxy
public partial class _Proxy : System.Web.UI.Page
protected void Page_Load(object sender, EventArgs e)
string proxyURL = string.Empty;
proxyURL = HttpUtility.UrlDecode(Request.QueryString[“u”].ToString());
catch { }

if (proxyURL != string.Empty)
HttpWebRequest request = (HttpWebRequest)WebRequest.Create(proxyURL);
request.Method = “GET”;
HttpWebResponse response = (HttpWebResponse)request.GetResponse();

if (response.StatusCode.ToString().ToLower() == “ok”)
string contentType = response.ContentType;
Stream content = response.GetResponseStream();
StreamReader contentReader = new StreamReader(content);
Response.ContentType = contentType;


[html]<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="Proxy.aspx.cs" Inherits="Proxy._Proxy" %>[/html]

The Proxy.aspx page is simply blank except for the Page tag. When passing the URL to the query string, it is important that it is URL encoded. This helps to prevent query strings of the remote site URL from interfering with the Proxy page.

Example Usage

ASP.NET Proxy Page Source

Happy coding!

Pin It on Pinterest

Share This
%d bloggers like this: