Request.RawUrl vs. Request.Url

Question

What is the difference between Request.RawUrl and Request.Url in ASP.NET?

score 70 · Answer 1 · edited May 20 '19 at 18:43

No one seems to have mentioned that it shows the Raw URL actually received by IIS, before any manipulation may have happened sending it around IIS or your file system with URL rewriting for example.

Say you have set an error page at /error in an MVC app and you set your webconfig to replace error pages with your custom error page at that location. In this way when getting an error at /faultypage, the user will get the page at /error but the url in your browser's address bar will still say www.mysite.com/faultypage—this is a transfer, or a rewrite.

Now on your error controller if you are to take a peek at Request.Url, it will be something like www.mysite.com/error and Request.RawUrl would say (more usefully?) /faultypage which is the user's actual request not the page that is currently being executed.

score 55 · Accepted Answer · edited Jul 25 '13 at 19:58

55

From MSDN:

The raw URL is defined as the part of the URL following the domain information. In the URL string http://www.contoso.com/articles/recent.aspx, the raw URL is /articles/recent.aspx.

This means, you can use rawurl and do not have to care about through which address the server was called (for instance http://yourserver/ or http://yourserver.yourdomain.com/ if you have multiple interfaces.)

However, the URL property of an HTTPRequest object returns a System.URI object, which also contains server name.

edited Jul 25 '13 at 19:58

Alex Shesterov

26,085
12
82
103

answered Jan 07 '10 at 11:09

naivists

32,681
5
61
85

16

This explanation incorrectly implies that `Request.RawUrl` is just syntactic sugar for `Request.Url.LocalPath`. – Brian Oct 16 '12 at 13:11
3

@Brian it might be helpful to explain how it's not just syntactic sugar. – Mal Ross Apr 04 '14 at 08:15
10

@MalRoss: They can be different paths entirely during path rewriting (e.g., 404 handlers). See [British Developer's answer](http://stackoverflow.com/a/20381367/18192) – Brian Apr 04 '14 at 13:15
One issue I can't resolve is how to get the default url. For example, I'll get just a "/" for localhost:53188, but what I want is localhost:53188/Home/Index – JoshYates1980 Sep 11 '14 at 21:39

score 18 · Answer 3 · edited May 23 '17 at 12:03

18

Request.RawUrl is very similar to Request.Url.PathAndQuery except that Request.Url.PathAndQuery includes the Default Document if one was used whereas Request.RawUrl does not. From my experience, this is true for ASP.Net 4.0 and higher.

edited May 23 '17 at 12:03

Community

1
1

answered May 04 '13 at 00:07

dana

17,267
6
64
88

score 6 · Answer 4 · edited Sep 29 '18 at 21:59

The HttpRequest.RawUrl Property documentation describes the property value as:

The raw URL is defined as the part of the URL following the domain information. In the URL string http://www.contoso.com/articles/recent.aspx, the raw URL is /articles/recent.aspx. The raw URL includes the query string, if present.

The HttpRequest.Url Property documentation describes the property value as:

A Uri object that contains the URL of the current request.

See the Uri class documentation for its properties.

score 5 · Answer 5 · edited May 23 '17 at 11:54

5

Request.RawUrl returns a string, it's everything after the domain information for the current url.

Eg, for: Request.RawUrl vs. Request.Url

Request.RawUrl would be /questions/2019735/request-rawurl-vs-request-url

Request.Url returns a Uri object, http://msdn.microsoft.com/en-us/library/system.uri_members.aspx

edited May 23 '17 at 11:54

Community

1
1

answered Jan 07 '10 at 11:10

Town

14,706
3
48
72

Request.RawUrl vs. Request.Url

5 Answers5

Linked