Prefixing every URL parameter with "field." produces ugly URLs
Bug #87229 reported by
Matthew Paul Thomas
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
In Launchpad forms, putting "field." at the start of the name for every field in a search form makes the result URLs longer, harder to read, and harder to hack. It would be nice if this practice could cease, with URLs containing field.foo=bar being permanently redirected to equivalent foo=bar URLs.
Revision history for this message
| Björn Tillenius (bjornt) wrote Re: [Bug 87229] Stop prefixing every URL parameter with "field." | #1 |
| description: | updated |
| Changed in launchpad: | |
| status: | Unconfirmed → Confirmed |
Revision history for this message
| Francis J. Lacoste (flacoste) wrote Re: Stop prefixing every URL parameter with "field." | #2 |
| Changed in launchpad-foundations: | |
| status: | Confirmed → Triaged |
| importance: | Undecided → Low |
To post a comment you must log in.
On Fri, Feb 23, 2007 at 02:04:47AM -0000, Matthew Paul Thomas wrote:
> Public bug reported:
>
> In Launchpad forms, putting "field." at the start of the name for every
> field in a search form makes the result URLs longer, harder to read, and
> harder to hack. It would be nice if this practice could cease, with URLs
> containing field.foo=bar being permanently redirected to equivalent
> foo=bar URLs.
At the moment this it's actually quite hard to get rid of the 'field.'
part due to limitations in Zope's form machinery. There are patches
upstream that we can pull it, though, to make it easier.
> (Fixing this would likely include removing the fix for bug 57621.)
No it won't, we still need to use prefixes in a few places. For example
on the bug page, where there is one form (with a unique prefix) for each
bug task.