Another thing that needs to be considered to apply this fix is how to
handle all the other weblog urls which we don't really want to support
both slash and non-slash versions of. i.e.
/weblog/entry/anchor vs. /weblog/entry/anchor/
/weblog/tags/foo+bar vs. /weblog/entry/foo+bar/
/weblog/category/Blah vs. /weblog/category/Blah/
I am going to consider the second version of these urls, the ones with a
trailing slash, to be considered 404s since there isn't anywhere that
these urls are formed or promoted by Roller and it seems easier to make
urls with trailing slashes be 404s rather than to try and setup special
redirects for every url to get around this issue.
So the only url that will support a trailing slash will be the actual
weblog index page url.
-- Allen
Allen Gilliland wrote:
I'm not sure there is really an issue there. Remember, both urls work
fine and can be used interchangeably, it's just that one of them is a
redirect to the other. So I don't see a problem with having people
distribute the /weblog form of the url and have that url be a redirect
to /weblog/. Websites all over the place do that to promote vanity urls
which are shorter and easier to remember and then just redirect to the
real location of the content.
I also prefer the /weblog/ version because *if* someone wants to do
static content generation at some point then you will want the weblog
homepage to be /weblog/ and not /weblog.
-- Allen
Sean Gilligan wrote:
I agree with Matt. If you want to print or publicize a URL you
probably don't want the trailing slash. If people go to the URL and
then bookmark it or email it, you don't want to confuse things by
having those bookmarks or emails have the the redirected (with
trailing slash) URL in them.
-- Sean
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. ;-)
Matt
What do others think? Is this something we should correct before 3.0
goes final?
-- Allen
