When can Request.Url be null?

asp.net-mvc-3 controller resharper
Mohayemin picture Mohayemin · Aug 27, 2012 · Viewed 7k times · Source

In my controller code I am using: Request.Url.<Something>. ReSharper suggests that Request.Url can be null.

So, when exactly can Request.Url be null? I am not talking about testing, I am interested only about an Application that is live / has already been deployed.

Please note that I have not received any NullReferenceExceptions from using Request.Url up to this point.

Answer

karaxuna picture karaxuna · Aug 27, 2012

HttpRequestBase is a class and ReSharper sees it as an actual Class, nothing more (theoretically, it can be null). So it does not analyze the usage of this specific Class.

In reality, I think that Request.Url will never be null, so just ignore ReSharper in this case.

Related questions

Multiple types were found that match the controller named 'Home'

I currently have two unrelated MVC3 projects hosted online. One works fine, the other doesn't work, giving me the error: Multiple types were found that match the controller named 'Home'. This can happen if the route that services this request (…

Read More
How to pass parameters to a partial view in ASP.NET MVC?

Suppose that I have this partial view: Your name is <strong>@firstName @lastName</strong> which is accessible through a child only action like: [ChildActionOnly] public ActionResult FullName(string firstName, string lastName) { } And I want to use …

Read More
asp.net mvc3 return raw html to view

Are there other ways I can return raw html from controller? As opposed to just using viewbag. like below: public class HomeController : Controller { public ActionResult Index() { ViewBag.HtmlOutput = "<HTML></HTML>"; return View(); } } @{ ViewBag.Title = "Index"; } @Html.…

Read More