Otto van der Schaaf

The relevant code is over at https://github.com/apache/incubator-pagespeed-ngx/blob/master/src/ngx_pagespeed.cc#L1892 AFAICT mod_pagespeed's `build_context_for_request()` is only called in the html filter. At a glance it seems the code linked above needs to moved so...

Well, it may take me a while before I get around to this, there are some other things in the project that are having higher priority at the moment.

@tobsch I haven't forgotten, but unfortunately I simply haven't got a chance to get around to it yet, sorry!

On a hunch, it looks like the module is not able to fetch its inputs over https when it needs to reconstruct an optimised resource on the fly when it's...

@mmokhi contributed a FreeBSD port of mod_pagespeed: https://svnweb.freebsd.org/changeset/ports/452011 X-Posting from mod-pagespeed-discuss: ``` The mod_pagespeed now exists as a port in official FreeBSD ports-tree (therefore pkg repository as well). You simply...

@denigmus As far as I know no-one currently is looking into ngx_pagespeed on FreeBSD. Having said that, @mmokhi's tackled nearly all of the technical platform challenges, so with that as...

I've been looking into the code that wires up the beacons pretty closely (see https://github.com/pagespeed/mod_pagespeed/pull/1375) and tested a couple of things in light of this issue. On the bleeding edge...

For `gzip_static`, I think it matters if the origin involved is low latency and high bandwidth or far off. Concretely, if a hypothetical ngx_pagespeed enabled proxy runs in front of...

Cross linking similar report on mps-discuss: https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/mod-pagespeed-discuss/cLE9qIYb_rg/KZceqhuwAgAJ

@Algram If you could share the url privately that would be helpful