Home/ Questions/Q 4000882
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-20T07:50:11+00:00

I have an asp.net 3.5 app. when I try to add a value to

  • 0

I have an asp.net 3.5 app. when I try to add a value to the url to be picked up in Request.PathInfo, i lose anything linked in head because the locations are resolved as relative paths.

master page looks like this:

<head id="Head1" runat="server">
    <link rel="stylesheet" href='~/App_Themes/main/style.css' type="text/css"  />
</head>

and renders like this

<head id="ctl00_ctl00_Head1">
    <link rel="stylesheet" href="../App_Themes/main/style.css" type="text/css" />
</head>

and so when i go to 

http://localhost:5000/project/folder/edit.aspx/555

the browser is looking for the stylesheet at 

http://localhost:5000/project/folder/App_Themes/main/style.css

instead of 

http://localhost:5000/project/App_Themes/main/style.css

is it automatic behavior to resolve with a relative path? can I change it? is this something the previous developer is doing that i haven’t found?

— edit —

i took the suggestion below and added a base element like so

<base id="ctl00_ctl00_baseElement" href="http://localhost:5000/project/"></base>

but my links still don’t work because asp.net is insistent on rendering the urls as relative paths unless the href starts with /, but in both cases i end up one level too high now.

http://localhost:5000/App_Themes/main/style.css
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Apparently when the head element is defined as a server control, link elements within are automatically parsed and resolved by the server. So the solution is to have the head element as a standard html control only or possibly manually add your link elements. I bailed on the PathInfo idea I was pursuing so I didn’t get that far.

    • 0