No, for any URI that isn’t completely well-formed, the browser works
out the rest of the path for any relative adresses from what’s known
as the base href. In a normal HTML page (one that hasn’t been tampered
with using rewrite, in other words) this is precisely the same as
removing the current page filename from the total URL. So if you were
at:
http://www.example.com/foo/bar/baz.html
the base href would be
http://www.example.com/foo/bar/
Now in a case where you have tampered with the URI, any relative
addresses would need to know the real starting point to add on to,
because the URI sent by the server to the browser is a complete
fiction. In your case, I’m guessing that the browser is thinking that
your tail-less filename is really a directory name, and isn’t coming
up with the right location for your other files. In effect, it’s
looking for them one directory level below where they really are.
There’s two ways to fix that. One is to make sure that any and all
resource URIs are made root relative, so instead of Resources/
image.jpeg, you would write /foo/bar/Resources/image.jpeg. The other
is to add a base href tag to the page, up in the head before any
relative links are processed:
<base href="http://example.com/foo/bar/" />
Then any relative URIs will be calculated with that as a starting point.
Walter
On Feb 28, 2011, at 4:47 PM, Todd wrote:
Are you using a base href directive in your pages? Is there any
difference between trailing slash and no trailing slash?
If you’re referring to manually typing the url then no, there’s no
difference if the trailing slash is included or not, some content is
missing either way.
I’m including <?php include('mycms/runtime.php'); ?> at the top of
the page, if that’s what you mean.
Todd
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options