Ticket #128 (closed enhancement: fixed)
Add support for 301 Moved Permanently to relocate verb
| Reported by: | scorfield | Owned by: | scorfield |
|---|---|---|---|
| Type: | enhancement | Priority: | normal |
| Milestone: | Fusebox 5.1 | Component: | Miscellaneous |
| Version: | 5.0 | Severity: | normal |
| Keywords: | Cc: |
Description
My feeling on this is to add type="moved" but there are other options:
Barney says:
I'd vote for a separate 'moved' verb, since the objective its to say
the page is no longer valid and you should try another, rather than a
transparent relocation. Subtle difference, but I think it would help
readability of circuit.xml by more clearly and obviously conveying
your intentions. I'm also not much of a fan of the existing
server/client distinction; I think there should have been separate
relocate and forward verbs.
Not going to work for 5.0, but perhaps down the road, 'type' on
relocate should be deprecated and a separate built-in lexicon with
some extra features should be incorporated. That lexicon would be
part of the cores and contain moved, forward, and maybe some other
verbs that are non-mainstream, but still generally useful.
cheers,
barneyb
On 7/11/06, Jordan Clark <jclark@imagineeringstudio.com> wrote:
I tried sending this message yesterday but it hasn't shown up, lets see
if this one goes through...
I'd like to suggest an addition to the relocate verb, when a url is
expired, outdated or gone the recommended way to move browsers and
crawlers to a new page is with a 301 "Moved permanently" redirection, as
opposed to the 302 "Object Temporarily Moved" which is what cflocation uses.
It only takes a few little changes to the verb to support this
functionality, I've attached the modified file. Let me know what you
think, maybe this small change could be included in the final release or
else in 5.1.
