Skip to content
This repository was archived by the owner on Apr 10, 2025. It is now read-only.
This repository was archived by the owner on Apr 10, 2025. It is now read-only.

Mod PageSpeed 0.10.21.2-1381 fails to retrieve combined objects with error, "Invalid escaped URL segment" #380

@GoogleCodeExporter

Description

@GoogleCodeExporter
What steps will reproduce the problem?
1. Upload the attached HTML document (pagespeed_test.html) to a pagespeed 
enabled server
2. Enable the PageSpeed filter combine_javascript
3. Create two bogus javascript files, /example_1.js and /example_2.js at the 
web document root. The contents of these files does not matter.
4. Access http://servername/pagespeed_test.html twice.

What is the expected output? What do you see instead?
Expected Behavior: The combined JavaScript file should be created and 
accessible by pagespeed.

Actual Behavior: PagSpeed combines the JavaScript files, but the combined file 
is inaccessible.  The HTTP response code is 404 when the browser makes the 
below request: 
http://servername/example_1.js+example_2.js.pagespeed.jc.ZKzOolut-6.js

The following error is present in the appache error log:
[Thu Feb 09 11:19:26 2012] [error] [mod_pagespeed 0.10.21.2-1381 @2121] Invalid 
escaped URL segment: example_1.js%2bexample_2.js

What version of the product are you using (please check X-Mod-Pagespeed
header)?
mod_pagespeed 0.10.21.2-1381

On what operating system?
# cat /etc/SuSE-release
openSUSE 11.4 (x86_64)
VERSION = 11.4
CODENAME = Celadon

# uname -a
Linux linux-ghzy 2.6.37.6-0.7-desktop #1 SMP PREEMPT 2011-07-21 02:17:24 +0200 
x86_64 x86_64 x86_64 GNU/Linux

Which version of Apache?
Apache/2.2.17 (Linux/SUSE)

Which MPM?
prefork

Please provide any additional information below, especially a URL or an
HTML file that exhibits the problem.

We are running the mod_pagespeed engine on Apache as a reverse-proxy to our web 
servers.

We did not see this issue in the previously released version: 0.10.19.5-1253

We see the same error when mod_pagespeed combines CSS files, however we had 
more difficulty reproducing this issue with CSS imports.

The issue may be unique to our environment.  We would be glad to provide more 
details if required.

Original issue reported on code.google.com by ericache...@gmail.com on 9 Feb 2012 at 5:07

Attachments:

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions