Matt Raible wrote:
On 9/27/06, Allen Gilliland <[EMAIL PROTECTED]> wrote:
I've come across a somewhat strange issue with the way weblog urls are
treated in Roller 3.0. With the new urls in Roller 3.0 both of these
are treated the same ...
/weblog
/weblog/
... and both will simply get you the index page for the given weblog.
The problem with lies in the fact that some clients will consider both
of those urls to be different and therefore it's misleading for them to
coexist when they represent the same page.
I did a little bit of reading on this topic and found that the general
concensus is that when you have a trailing slash issue with a url that
you should pick one version or the other as the preferred url and have
the alternative(s) simply do redirects to the preferred version.
The primary impact of this issue comes with metrics gathering and search
indexing because in both cases it can cause unwanted behavior to have 2
urls pointing to the same content. So, it may make some sense go ahead
and resolve this issue by choosing which form of the url we would prefer
and setting up a redirect for the alternative version.
I would suggest this ...
/weblog/ (preferred)
/weblog -> /weblog/
I'd rather see it the other way around - after all,
http://raibledesigns.com/page/rd doesn't redirect to
http://raibledesigns.com/page/rd/. Then again, trailing slashes annoy me
for
some reason. ;-)
Just the idea of this whole trailing slash issue is annoying to me, but
sadly I think it's going to be one of those stupid things that we just
have to deal with.
The main reason I suggested that /weblog/ be the preferred url is for
consistency. All of the weblog urls now are under /weblog/*, so I think
it makes the most sense if the root page for the weblog is /weblog/.
Also, supposedly this issue can cause problems with relative links which
depend on trailing slashes. I haven't seen that happen in Roller
templates on 3.0 yet, but I suppose it's possible. That would be
another reason to use /weblog/ instead of /weblog, so that someone could
put an anchor in their templates like "resources/foo.jpg" and it
functions as /weblog/resource/foo.jpg, where if the weblog url was
/weblog then that same relative link becomes /resources/foo.jpg and
doesn't work.
-- Allen
Matt
What do others think? Is this something we should correct before 3.0
goes final?
-- Allen
