This repository has been archived by the owner on Apr 21, 2023. It is now read-only.

Mixed-case paths broken in domain-mapping directives #692

Closed

GoogleCodeExporter opened this issue Apr 6, 2015 · 3 comments

Labels

auto-migrated Milestone-v31 Priority-Medium release-note Type-Defect

GoogleCodeExporter commented Apr 6, 2015

When DomainLawyer was written we could only work with Origins -- we couldn't 
authorize or map to subpaths.  So lower-casing the whole URL prefix was fine.

However now we support sub-paths in domain-mapping commands and I think we 
lower-case them, so mixed-case ones won't match.

Original issue reported on code.google.com by jmara...@google.com on 9 May 2013 at 11:54

The text was updated successfully, but these errors were encountered:

GoogleCodeExporter added Priority-Medium Type-Defect auto-migrated release-note Milestone-v31 labels

Author

GoogleCodeExporter commented Apr 6, 2015

Original comment by jmara...@google.com on 11 Nov 2013 at 6:54

Changed state: Started

Author

GoogleCodeExporter commented Apr 6, 2015

Fixed in https://code.google.com/p/modpagespeed/source/detail?r=3621

Original comment by jmara...@google.com on 12 Nov 2013 at 3:05

Changed title: Mixed-case paths broken in domain-mapping directives
Added labels: Milestone-v31, release-note

Author

GoogleCodeExporter commented Apr 6, 2015

Original comment by jmara...@google.com on 12 Nov 2013 at 3:05

Changed state: Fixed

GoogleCodeExporter closed this as completed

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.