Another topic on "Cannot use a leading .. to exit above the top directory"

webonomic · Jan 18, 2006

A number of topics ask how to solve the "Cannot use a leading .. to
exit above the top directory" error.

I am having the same problem with an asp.net 2.0 website. The site
works fine on Localhost, but not when I move the site to my hosting
company.

I've read that turning the Parent Paths option to ON in the IIS
properties should do the trick. It is ON for both my localhost and my
online host. Only the localhost still works.

I've switched hardcoded links from "../app/mypage.aspx" where ../
(brings you to the Root directory) to "/app/mypage.aspx" thinking that
the ".." is what is causing the problem.

The site implements a Masterpage in the root directory.

Maybe this is some kind of permissions thing?

Please please help!

webonomic · Jan 20, 2006

After some careful fiddling around for a couple hours, I figured out
what the problem was. First of all, note that Parent Paths has nothing
to do with the issue. They can be on or off.

If your head section has the runat server (<head runat="server">), and
you are using Masterpages, and aren't or are using Themes but still
have a <link href="../styles/styles.css" rel="stylesheet" /> in your
Head section, because the Head section is process at the server, it
will add at least one but could be more " ../ ".

If you use themes, take out the <link href....>. Using themes will
automatically link any CSS in your Theme directory and will link with
the proper

The ../ is also added to some other HTML elements like the FAVICON
link.

For stylesheets, you can still use
<style type="text/css">
@import "../styles/layout.css";
</style>
Asp.net will not add a ../ to that.

You can also do this:
<script type="text/javascript">
//<![CDATA[
document.write('<link rel="Stylesheet" type="text/css" href="<%=
Page.ResolveUrl("~/styles/styles.css") %>" />');
and it will work. This was posted on
http://www.telerik.com/Default.aspx?PageId=2202&b311D=orJO1
and was what made me realize that the extra ../ get's added to elements
when you have the runat server in the Head.

Please note that you cannot simply use HTML comments () to
comment out any hardcoded <link rel=stylesheet> elements. So what I
mean is, you cannot go

You MUST use Asp.Net comment code:
<%= <link href="../styles/styles.css" rel="stylesheet" /> -->

As far as I can, after hours of searching, this is THE solution.

- your us
If you have this problem

Cannot use a leading .. to exit above the top directory.	2	May 8, 2005
Error: Cannot use a leading .. to exit above the top directory.	2	Dec 15, 2005
Cannot use a leading .. to exit above the top directory.	2	May 12, 2007
Error: Cannot use a leading .. to exit above the top directory.	5	May 30, 2005
Cannot use a leading .. to exit above the top directory.	1	Dec 11, 2003
Cannot use a Leading .. Error	5	Nov 10, 2005
simple_html_dom: simple use-case - getting a scipt to work	0	Mar 2, 2020
Working With Files Above Site's Root Directory	4	Dec 23, 2004

Another topic on "Cannot use a leading .. to exit above the top directory"

webonomic

webonomic

Ask a Question

Similar Threads

Members online

Forum statistics

Latest Threads