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

Increase the URL segment limitations imposed by Apache #176

Closed
GoogleCodeExporter opened this issue Apr 6, 2015 · 4 comments
Closed

Increase the URL segment limitations imposed by Apache #176

GoogleCodeExporter opened this issue Apr 6, 2015 · 4 comments

Comments

@GoogleCodeExporter
Copy link

With help from folks on modules-dev@httpd.apache.org we now have some ideas on 
how to relax our 256 character limitation on URL segments.  This can help us to 
combine more files (css files currently) than we are currently able to:

Ben Noordhuis to modules-dev
> I'm pretty sure it was
> due to some built-in filter or core element in httpd trying to map the URL
> to a filename (which is not necessary as far as mod_pagespeed is concerned)
> and bumping into an OS path limitation (showing up as 403 Forbidden).

This might be the doing of core_map_to_storage(). Never run into it
myself (with URLs up to 4K, anyway) but there you go.

Okay, here is a dirty secret: if you hook map_to_storage and return
DONE, you bypass Apache's authentication stack - and nearly all other
hooks too. Probably an exceedingly bad idea.

You can however use it to prevent core_map_to_storage() from running.
Just return OK and you're set.

Original issue reported on code.google.com by jmara...@google.com on 4 Jan 2011 at 11:28

@GoogleCodeExporter
Copy link
Author

Original comment by jmara...@google.com on 12 Jan 2011 at 5:06

  • Changed state: New

@GoogleCodeExporter
Copy link
Author

I have a fix in flight based on Ben's suggestion, which was spot-on.  But a 
quick note for the record from Ben:

  "a lot of software out there a hard limit on URL lengths (500-and-something is very common).  With Apache: mod_proxy and its providers do a lot of path mangling,"

So the fix will come with a workaround in the form of a directive to ratchet 
down the number of characters we are willing to expand a URL to.  Right now I 
want to stay on the aggressive side because it is somewhat crippling to a 
rewriter to be so limited in path length.

Original comment by jmara...@google.com on 19 Jan 2011 at 6:07

@GoogleCodeExporter
Copy link
Author

Fixed in r380

Original comment by jmara...@google.com on 19 Jan 2011 at 8:03

  • Changed state: Fixed

@GoogleCodeExporter
Copy link
Author

Original comment by sligocki@google.com on 19 Jan 2011 at 8:29

  • Added labels: release-note

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

No branches or pull requests

1 participant