Why does HttpContext.Current.Request.Url.AbsolutePath return an empty string?

Question

When user requests http://localhost/WebApp1/Default.aspx, txtApplicationPath.Text should be assigned “/WebApp1”, while txtAbsolutePath.Text should be assigned “http://localhost/WebApp1/Default.aspx”, but instead both textboxes display empty strings.

Why?

Default.aspx:

<asp:TextBox ID="txtApplicationPath" runat="server" 
    Text='<%# HttpContext.Current.Request.ApplicationPath %>'>
</asp:TextBox> <br />
<asp:TextBox ID="txtAbsolutePath" runat="server" 
    Text='<%# HttpContext.Current.Request.Url.AbsolutePath %>'>
</asp:TextBox>

thank you

I had the same result. It'll work if you populate those TextBoxes in code-behind instead of markup. — DOK
– DOK, Commented Oct 6, 2010 at 19:59
Ups, reason it didn't work is because I forgot to call Page.Databind — user437291
– user437291, Commented Oct 6, 2010 at 20:12

user468524 · Accepted Answer · 2010-10-06 22:39:26Z

2

if you want the full url you should use Request.Url.OriginalString, because AbsolutePath will omit the host part of the url.

answered Oct 6, 2010 at 22:39

user468524

1072 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Why does HttpContext.Current.Request.Url.AbsolutePath return an empty string?

1 Answer 1

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related