Bug Description

The restricted librarian generates non-canonical form urls, these can then be changed by canonicalising clients / intermediaries. Changing the restricted librarian urls causes the token to not match and a 404 - file not found - is returned to the client.

Apache without the nocanon config option will canonicalise, and some browsers like Chrome are known to canonicalise too.

Fairly simple file names - 'foo+bar.txt' - will show this problem.

Workarounds
===========

Use Firefox, run apache with nocanon on proxypass rules. We are currently doing the latter in the Canonical datacentre.

Proposed solutions
==================

* Change the url generation in Launchpad to be canonicalised, then canonicalisation will not change the url and things will Just Work.

On Thu, Jan 26, 2012 at 2:35 AM, Andreas Hasenack <email address hidden> wrote:
> Do you have a ticket for the chromium bug? They do make new releases
> frequently and we could perhaps get someone's attention over there.

AIUI it is deliberate on chromiums part, so we haven't opened a
ticket. As noted we can workaround it here by issuing canonicalised
urls, though that shouldn't be needed.