New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rewriting images fails to load original image from alternative port #107

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

Comments

Projects
None yet
1 participant
@GoogleCodeExporter

GoogleCodeExporter commented Apr 6, 2015

What steps will reproduce the problem?
1. I'm running a version of apache under a proxy . The site is configured to 
port  localhost:8080
2. Image rewrite requests are going to just 127.0.0.1 instead of 127.0.0.1:8080 
3. See error below.

What is the expected output? What do you see instead?

Expect to 


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

[mod_pagespeed 0.9.8.1-215] http://127.0.0.1/stylesheets/base_7189.css:0: 
serf_context_run error status=111 (Connection refused)


On what operating system?

Ubuntu 

Which version of Apache?

2.29

Which MPM?

Worker

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



Original issue reported on code.google.com by john%pro...@gtempaccount.com on 21 Nov 2010 at 9:43

@GoogleCodeExporter

This comment has been minimized.

GoogleCodeExporter commented Apr 6, 2015

The 'worker' MPM has not been tested; only pre-fork.  But this seems unrelated 
to this issue.  We'd love to hear about your experiences on the 'worker' MPM 
once this is resolved.

Can you give a more complete set of logs like this:
  1. set your loglevel to 'info'
  2. stop your server
  3. delete your log
  4. start your server
  5. refresh your page from your browser
  6. attach the contents of the log to this Issue
That might tell us some useful things (as well as a few things we'll need to 
ignore).  You'll want to set your loglevel back to 'warn' or something after 
that so you don't fill your disk.

Other information that would be useful:

 - any ModPagespeedDomain lines in your conf file
 - the URL you used in your browser to exhibit this behavior
 - the HTML fragment referencing stylesheets/base_7189.css

Original comment by jmara...@google.com on 21 Nov 2010 at 12:24

@GoogleCodeExporter

This comment has been minimized.

GoogleCodeExporter commented Apr 6, 2015

Here is the additional information: 

The configuration is as follows:
1)     ModPagespeedDomain http://staging.zoomin.co.nz
    ModPagespeedDomain http://images.zoomin.co.nz
2) http://staging.zoomin.co.nz is a proxy to an internal address 127.0.0.1:8080 
.
3) I hit "http://staging.zoomin.co.nz" to get the behaviour.
4) CSS <link href="/stylesheets/base_7189.css" media="screen" rel="Stylesheet" 
type="text/css"/>

Original comment by john%pro...@gtempaccount.com on 21 Nov 2010 at 8:32

Attachments:

@GoogleCodeExporter

This comment has been minimized.

GoogleCodeExporter commented Apr 6, 2015

How are you setting up the proxy to 127.0.0.1:8080.

By the way we have added new conf file directives ModPagespeedMapRewriteDomain 
and ModPagespeedMapOriginDomain so that we can do this transformation for you 
in mod-pagespeed.

This is in the SVN trunk but is not in the branch made last friday or the 
binary release we will make this week.

Original comment by jmara...@google.com on 23 Nov 2010 at 4:42

@GoogleCodeExporter

This comment has been minimized.

GoogleCodeExporter commented Apr 6, 2015

This is fixed via the directive ModPagespeedMapOriginDomain.  See the FAQ.

Original comment by jmara...@google.com on 3 Dec 2010 at 11:13

  • Changed state: Fixed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment