jmarantz commented on issue #1319: image 404s, probably due to ipro-recorded
resources falling out of cache with failing fetch
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1319#issuecomment-386899654
@oschaaf we lost track of this one a couple of years ago, as
oschaaf commented on issue #1319: image 404s, probably due to ipro-recorded
resources falling out of cache with failing fetch
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1319#issuecomment-387016076
@jmarantz Looking at the code I think ngx_pagespeed `Disallow`
jmarantz commented on issue #1319: image 404s, probably due to ipro-recorded
resources falling out of cache with failing fetch
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1319#issuecomment-387064987
Cool. My theory is that it's still being ipro-rewritten because it's a
oschaaf commented on issue #1319: image 404s, probably due to ipro-recorded
resources falling out of cache with failing fetch
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1319#issuecomment-387092354
It looks like `.pagespeed.`resources will be fetched regardless of any
edeis53 commented on issue #1704: Redis cache TTL
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/1704#issuecomment-387566711
I would suggest a default -1 expiry to match current pagespeed config
behaviour, and yes we'd probably use a long TTL like 1 year in our config.
oschaaf commented on issue #1556: Combined css returns truncated, mis-encoded
body on cache hit
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1556#issuecomment-388730282
@jstangroome awesome, I have it reproduced now!
So one prerequisite that I think exists for the
jstangroome commented on issue #1556: Combined css returns truncated,
mis-encoded body on cache hit
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1556#issuecomment-388756405
>the first request happens without Accept-Encoding: gzip
@oschaaf all my testing, in
oschaaf commented on issue #1556: Combined css returns truncated, mis-encoded
body on cache hit
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1556#issuecomment-388759087
Well actually .. in the script that demonstrates the issue there is:
```
good_css_url=$(curl
jstangroome commented on issue #1556: Combined css returns truncated,
mis-encoded body on cache hit
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1556#issuecomment-388761430
True, I had forgotten about that. I guess a non-gzip request for the HTML
may have lead to
oschaaf closed pull request #1559: Properly iterate modules looking for gzip
commands
URL: https://github.com/apache/incubator-pagespeed-ngx/pull/1559
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of
oschaaf commented on issue #1556: Combined css returns truncated, mis-encoded
body on cache hit
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1556#issuecomment-389066123
So I caught the http cache in gdb writing the bad entry. The C-L is 7411
with C-E gzip, but the body
oschaaf commented on issue #1556: Combined css returns truncated, mis-encoded
body on cache hit
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1556#issuecomment-389077301
The change above doesn't help. It probably wouldn't have been the right fix,
but naively I would have
edeis53 commented on issue #1704: Redis cache TTL
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/1704#issuecomment-387212216
Essentially, all that should be required is swapping the SET command with
SETEX, and defining a default for the TTL to -1 (no expiry). Then defining
edeis53 commented on issue #1704: Redis cache TTL
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/1704#issuecomment-387212216
Essentially, all that should be required is swapping the SET command with
SETEX, and defining a default for the TTL to -1 (no expiry), which will
oschaaf commented on issue #1556: Combined css returns truncated, mis-encoded
body on cache hit
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1556#issuecomment-387686294
That is some really good information. Intuitively I'd think that there is an
issue specific to
jstangroome opened a new issue #1556: Combined css returns truncated,
mis-encoded body on cache hit
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1556
PageSpeed 1.13.35.2 on nginx 1.13.8 on Ubuntu 14.04 (and on Minikube).
Original HTML contains:
```
edeis53 commented on issue #1704: Redis cache TTL
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/1704#issuecomment-387566711
I would suggest a default -1 expiry to match current pagespeed config
behaviour, and yes we'd probably use a long TTL like 1 year in our config.
oschaaf commented on issue #1704: Redis cache TTL
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/1704#issuecomment-387341073
https://github.com/pagespeed/mod_pagespeed/pull/1627/files shows plumbing
that is similar to what would be needed to implement this.
jstangroome commented on issue #1556: Combined css returns truncated,
mis-encoded body on cache hit
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1556#issuecomment-387757910
Is pagespeed expecting nginx to do the gzipping of the response? My
nginx.conf does not contain
oschaaf commented on issue #1556: Combined css returns truncated, mis-encoded
body on cache hit
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1556#issuecomment-387774687
In this scenario, nginx is not expected to play a role in the gzipping.
As a workaround, adding
jstangroome commented on issue #1556: Combined css returns truncated,
mis-encoded body on cache hit
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1556#issuecomment-387753373
I've just realised that the failed response is not being truncated by
pagespeed. My tests with
jstangroome commented on issue #1556: Combined css returns truncated,
mis-encoded body on cache hit
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1556#issuecomment-387745691
@oschaaf I have posted the error.log with debug-level logging on nginx built
`--with-debug` as a
RajaHassan commented on issue #1758: ModPagespeedHonorCsp ignores that
unsafe-eval is not an allowed script source
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/1758#issuecomment-384929638
can anybody tell that is this issue being fixed ?
oschaaf commented on issue #1552: Honor assume yes when installing dependencies
URL:
https://github.com/apache/incubator-pagespeed-ngx/pull/1552#issuecomment-384973046
Code change looks good, and in terms of function it looks like this makes a
lot of sense.
I have to dive in some more
oschaaf commented on issue #1758: ModPagespeedHonorCsp ignores that unsafe-eval
is not an allowed script source
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/1758#issuecomment-384974178
@RajaHassan As far as I know, no-one is working to fix this right now.
Not sure if
dsanders11 opened a new pull request #1552: Honor assume yes when installing
dependencies
URL: https://github.com/apache/incubator-pagespeed-ngx/pull/1552
Currently running `build_ngx_pagespeed.sh` with `--assume-yes` won't
automatically send yes when installing dependencies, defeating
eldk commented on issue #1761: MapProxyDomain don't rewrite nor proxy pictures
included in javascript
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/1761#issuecomment-385013034
Hello,
I have modified /mod_pagespeed_example/proxy_external_resource.html -
eldk commented on issue #1761: MapProxyDomain don't rewrite nor proxy pictures
included in javascript
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/1761#issuecomment-385013034
Hello,
I have modified /mod_pagespeed_example/proxy_external_resource.html -
eldk commented on issue #1761: MapProxyDomain don't rewrite nor proxy pictures
included in javascript
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/1761#issuecomment-385013034
Hello,
I have modified /mod_pagespeed_example/proxy_external_resource.html -
jmarantz commented on issue #1761: MapProxyDomain don't rewrite nor proxy
pictures included in javascript
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/1761#issuecomment-385018037
This is expected behavior. Pagespeed does not attempt to rewrite URLs
embedded in
jmarantz commented on issue #1761: MapProxyDomain don't rewrite nor proxy
pictures included in javascript
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/1761#issuecomment-385018037
This is expected behavior. Pagespeed does not attemptto rewrite URLs
embedded in
oschaaf closed pull request #1552: Honor assume yes when installing dependencies
URL: https://github.com/apache/incubator-pagespeed-ngx/pull/1552
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As
dsanders11 commented on issue #1552: Honor assume yes when installing
dependencies
URL:
https://github.com/apache/incubator-pagespeed-ngx/pull/1552#issuecomment-385091110
Perhaps all the dependencies are installed in the case of `--devel` (or
already on the server). I believe if it found
oschaaf closed pull request #1553: Add wget as dependency for Debian-based
distros in build script
URL: https://github.com/apache/incubator-pagespeed-ngx/pull/1553
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake
oschaaf commented on issue #1556: Combined css returns truncated, mis-encoded
body on cache hit
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1556#issuecomment-387895462
I suspect that impact on required cache space of the workaround may not be
that big: images probably
jstangroome commented on issue #1556: Combined css returns truncated,
mis-encoded body on cache hit
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1556#issuecomment-387899755
I've confirmed that the seemingly unrelated `Content-Length: 105759`
response header in the
jstangroome commented on issue #1556: Combined css returns truncated,
mis-encoded body on cache hit
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1556#issuecomment-387894703
For reference, I've added another gist showing the hex dump of the cached
file header and
jstangroome commented on issue #1556: Combined css returns truncated,
mis-encoded body on cache hit
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1556#issuecomment-387894703
For reference, I've added another gist showing the hex dump of the cached
file header and
berengerzyla commented on issue #1545: server push not working while pagespeed
is set to on
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1545#issuecomment-387941159
I have been scratching my head over this one too, and it's not a duplicate
of #1539 .
Activating
berengerzyla commented on issue #1545: server push not working while pagespeed
is set to on
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1545#issuecomment-387941792
Strange thing is even with all the filters deactivated, PageSpeed will try:
`Trying to serve rewritten
Thedemon007 opened a new issue #1557: Optimized javascript is not compressed
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1557
When downloading to .js.pagespeed. file in specific, the server
response with header Content-Encoding: gzip however it is not compressed.
dsanders11 commented on issue #1559: Properly iterate modules looking for gzip
commands
URL:
https://github.com/apache/incubator-pagespeed-ngx/pull/1559#issuecomment-388623231
The CI failure seems to be a transient failure relating to the job taking
too long. Might have had to do with
jmarantz commented on issue #1557: Optimized javascript is not compressed
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1557#issuecomment-388624209
What you are seeing when you disable memcached is effectively a pagespeed
server-side cache-flush. It won't make any
jmarantz commented on issue #1557: Optimized javascript is not compressed
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1557#issuecomment-388624209
What you are seeing when you disable memcached is effectively a pagespeed
server-side cache-flush. It won't make any
dsanders11 opened a new pull request #1558: Fix setting 'gzip_proxied' when
applying gzip settings
URL: https://github.com/apache/incubator-pagespeed-ngx/pull/1558
This fix should be fairly self-explanatory when viewing the code, but the
code was setting the wrong command (and may have
Thedemon007 commented on issue #1557: Optimized javascript is not compressed
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1557#issuecomment-388621097
I tried stop varnish temporarily but not have changes, i can confirm the
problem no is varnish the problem is related
oschaaf commented on issue #1559: Properly iterate modules looking for gzip
commands
URL:
https://github.com/apache/incubator-pagespeed-ngx/pull/1559#issuecomment-388625763
Thanks! I suspect that this is effectively a no-op, but regardless I feel it
is a solid improvement as it makes
oschaaf commented on issue #1559: Properly iterate modules looking for gzip
commands
URL:
https://github.com/apache/incubator-pagespeed-ngx/pull/1559#issuecomment-388625787
(Also -- CI is passing, I restarted it. The previous try timed out indeed).
dsanders11 opened a new pull request #1559: Properly iterate modules looking
for gzip commands
URL: https://github.com/apache/incubator-pagespeed-ngx/pull/1559
This change may or may not be needed. I spent a frustratingly long time
trying to get gzip working with `ngx_pagespeed` in
oschaaf closed pull request #1558: Fix setting 'gzip_proxied' when applying
gzip settings
URL: https://github.com/apache/incubator-pagespeed-ngx/pull/1558
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of
oschaaf commented on issue #1558: Fix setting 'gzip_proxied' when applying gzip
settings
URL:
https://github.com/apache/incubator-pagespeed-ngx/pull/1558#issuecomment-388625511
LGTM, nice catch!
/cc @keesspoelstra
This
Thedemon007 commented on issue #1557: Optimized javascript is not compressed
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1557#issuecomment-388593338
I'm sure something happens with the compression, firefox show this message
Thedemon007 commented on issue #1485: s-maxage stuck on
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/1485#issuecomment-388517818
I have s-maxage=10 header in nginx server
This is an automated message from
jstangroome commented on issue #1556: Combined css returns truncated,
mis-encoded body on cache hit
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1556#issuecomment-388665742
@oschaaf This seems to be enough to reproduce the issue 90% of the time:
jstangroome commented on issue #1556: Combined css returns truncated,
mis-encoded body on cache hit
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1556#issuecomment-388665742
@oschaaf This seems to be enough to reproduce the issue 90% of the time:
Thedemon007 commented on issue #1557: Optimized javascript is not compressed
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1557#issuecomment-388658952
The server has been previously configured varnish with nginix via
proxy_pass, I have tried in various ways to disable
jstangroome commented on issue #1556: Combined css returns truncated,
mis-encoded body on cache hit
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1556#issuecomment-388261484
I've done some further investigation.
The URL that is failing doesn't exactly match the URL
jstangroome commented on issue #1556: Combined css returns truncated,
mis-encoded body on cache hit
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1556#issuecomment-388261484
I've done some further investigation.
The URL that is failing doesn't exactly match the URL
jmarantz commented on issue #1704: Redis cache TTL
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/1704#issuecomment-387400092
@oschaaf thanks for pulling up the example. I missed in the PR review that
the DB-index is not in the map key. I think it needs to be incorporated
oschaaf commented on issue #1771: Redis DB index aliasing
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/1771#issuecomment-387449218
Ugh, looks like you are right, nice catch.
This is an automated message from
philrice commented on issue #1319: image 404s, probably due to ipro-recorded
resources falling out of cache with failing fetch
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1319#issuecomment-386833970
thanks for the quick answer - yeah seems to be working , at least no
jmarantz commented on issue #1704: Redis cache TTL
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/1704#issuecomment-387413295
RE the original premise of this feature-request; I have a couple of
questions:
1. Won't Redis evict uninteresting keys based on some
philrice commented on issue #1319: image 404s, probably due to ipro-recorded
resources falling out of cache with failing fetch
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1319#issuecomment-386811108
I know this has been a while but im getting this behaviour in 1.14.0
oschaaf commented on issue #1560: SSI include fails with pagespeed in more
complex scenarios
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1560#issuecomment-389103282
Detailed error logs at the debug level for these scenarios would be helpful
in analysing this more -- if
chaihongjun commented on issue #1562: PageSpeed Serf fetch failure rate
extremely high; only 0 of 44 recent fetches fully successful
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1562#issuecomment-389783191
@rickygm your setting is correct
pagespeed
Lofesa commented on issue #1562: PageSpeed Serf fetch failure rate extremely
high; only 0 of 44 recent fetches fully successful
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1562#issuecomment-389434823
Hi
pagespeed LoadFromFileRuleMatch disallow .*; is the rigth
oschaaf commented on issue #1563: again the error: [ngx_pagespeed 1.13.35.2-0]
PageSpeed Serf fetch failure rate extremely high; only 0 of 44 recent fetches
fully successful; is fetching working?
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1563#issuecomment-390170591
In
Lofesa commented on issue #1563: again the error: [ngx_pagespeed 1.13.35.2-0]
PageSpeed Serf fetch failure rate extremely high; only 0 of 44 recent fetches
fully successful; is fetching working?
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1563#issuecomment-390395668
Hi
Lofesa commented on issue #1563: again the error: [ngx_pagespeed 1.13.35.2-0]
PageSpeed Serf fetch failure rate extremely high; only 0 of 44 recent fetches
fully successful; is fetching working?
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1563#issuecomment-390471808
rickygm commented on issue #1563: again the error: [ngx_pagespeed 1.13.35.2-0]
PageSpeed Serf fetch failure rate extremely high; only 0 of 44 recent fetches
fully successful; is fetching working?
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1563#issuecomment-390440799
Hi
Mag8891 commented on issue #1512: Installing NGINX with 1.13.35.1-beta fails
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1512#issuecomment-390505506
prior to install nginx pagespeed module as specified in source
instructions need to install more dependencies, here is
Mag8891 commented on issue #1512: Installing NGINX with 1.13.35.1-beta fails
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1512#issuecomment-390505506
prior install need to install more dependancies, here is full list that
worked for me
apt-get -y install
rickygm commented on issue #1563: again the error: [ngx_pagespeed 1.13.35.2-0]
PageSpeed Serf fetch failure rate extremely high; only 0 of 44 recent fetches
fully successful; is fetching working?
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1563#issuecomment-390524116
Hi
oschaaf closed issue #1562: PageSpeed Serf fetch failure rate extremely high;
only 0 of 44 recent fetches fully successful
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1562
This is an automated message from
oschaaf commented on issue #1562: PageSpeed Serf fetch failure rate extremely
high; only 0 of 44 recent fetches fully successful
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1562#issuecomment-389854760
@rickygm for setting up https fetching, reading
rickygm commented on issue #1562: PageSpeed Serf fetch failure rate extremely
high; only 0 of 44 recent fetches fully successful
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1562#issuecomment-389541737
Hi Lofesa , I'm using letsencrypt , and I'm not sure if it's the right
morlovich commented on issue #1556: Combined css returns truncated, mis-encoded
body on cache hit
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1556#issuecomment-389527574
On Tue, May 15, 2018 at 3:53 AM Otto van der Schaaf <
notificati...@github.com> wrote:
>
oschaaf commented on issue #1560: SSI include fails with pagespeed in more
complex scenarios
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1560#issuecomment-389100057
The segfault probably happens when dereferencing the recorder here:
oschaaf closed issue #1554: ngx_pagespeed.so not created
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1554
This is an automated message from the Apache Git Service.
To respond to the message, please log on
oschaaf commented on issue #1554: ngx_pagespeed.so not created
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1554#issuecomment-389149438
ngx_pagespeed just isn't included in the nginx ppa, sorry
This is an
jvnn opened a new issue #1560: SSI include fails with pagespeed in more complex
scenarios
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1560
I ran into some issues with SSI support when doing testing with pagespeed.
Using Nginx 1.13.9 and ngx_pagespeed 1.13.35.2-0, built
jvnn commented on issue #1560: SSI include fails with pagespeed in more complex
scenarios
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1560#issuecomment-389101610
One more detail, the content of the request line might be of interest:
```
request_line = {len = 34,
oschaaf commented on issue #1556: Combined css returns truncated, mis-encoded
body on cache hit
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1556#issuecomment-389603258
@morlovich
Yeah, I have been looking at that too..
What I think is *really* odd is that
Lofesa commented on issue #1563: again the error: [ngx_pagespeed 1.13.35.2-0]
PageSpeed Serf fetch failure rate extremely high; only 0 of 44 recent fetches
fully successful; is fetching working?
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1563#issuecomment-390606144
StormRU commented on issue #1073: Support FreeBSD
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/1073#issuecomment-391044757
Hi!
I have installed mod_pagespeed. I am running Apache 2.4.33
Google's doc says that i should use mod_pagespeed_ap24.so, but we only have
StormRU commented on issue #1073: Support FreeBSD
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/1073#issuecomment-391044757
Hi!
I have installed mod_pagespeed. I am running Apache 2.4.33
Google's doc says that i should use mod_pagespeed_ap24.so, but we only have
Lofesa commented on issue #1563: again the error: [ngx_pagespeed 1.13.35.2-0]
PageSpeed Serf fetch failure rate extremely high; only 0 of 44 recent fetches
fully successful; is fetching working?
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1563#issuecomment-391250548
Hi
rickygm commented on issue #1563: again the error: [ngx_pagespeed 1.13.35.2-0]
PageSpeed Serf fetch failure rate extremely high; only 0 of 44 recent fetches
fully successful; is fetching working?
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1563#issuecomment-391558230
Hi
oschaaf commented on issue #1565: How to disable POST ngx_pagespeed_beacon?
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1565#issuecomment-391610655
See https://www.modpagespeed.com/doc/faq#control_beacons
oschaaf closed issue #1565: How to disable POST ngx_pagespeed_beacon?
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1565
This is an automated message from the Apache Git Service.
To respond to the message,
rickygm commented on issue #1563: again the error: [ngx_pagespeed 1.13.35.2-0]
PageSpeed Serf fetch failure rate extremely high; only 0 of 44 recent fetches
fully successful; is fetching working?
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1563#issuecomment-391142453
Lofesa commented on issue #1563: again the error: [ngx_pagespeed 1.13.35.2-0]
PageSpeed Serf fetch failure rate extremely high; only 0 of 44 recent fetches
fully successful; is fetching working?
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1563#issuecomment-391991528
Lofesa commented on issue #1563: again the error: [ngx_pagespeed 1.13.35.2-0]
PageSpeed Serf fetch failure rate extremely high; only 0 of 44 recent fetches
fully successful; is fetching working?
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1563#issuecomment-391991528
mbautista opened a new issue #1566: BeaconUrl uses HTTP instead of HTTPS +
LoadFromFile not working
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1566
Hello,
We experience 2 problems since we moved from :
Linux Debian 8.8 + nginx 1.10.3 + ngx_pagespeed 1.11.33.2-0
Lofesa commented on issue #1566: BeaconUrl uses HTTP instead of HTTPS +
LoadFromFile not working
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1566#issuecomment-392248625
Perhaps is not related, but I think you need to configure ssl certificates
pagespeed
rickygm commented on issue #1563: again the error: [ngx_pagespeed 1.13.35.2-0]
PageSpeed Serf fetch failure rate extremely high; only 0 of 44 recent fetches
fully successful; is fetching working?
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1563#issuecomment-391792273
I
bantilan opened a new issue #1561: Rewrite Domain doesn't work when type
attribute comes first before src
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1561
Hi guys,
I have problem with the Rewrite Domain, to replace all of the resources to
CDN link..
In my
oschaaf commented on issue #1556: Combined css returns truncated, mis-encoded
body on cache hit
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1556#issuecomment-390896994
So the following diff helps with the bad content-length and mismatching c-e
headers:
```
Softhony opened a new issue #1564: Videotutorial ¿Cómo instalar pagespeed? En
español
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1564
Amigos he realizado un video tutorial para compartir con ustedes mi
experiencia instalando el módulo velocista
rickygm commented on issue #1563: again the error: [ngx_pagespeed 1.13.35.2-0]
PageSpeed Serf fetch failure rate extremely high; only 0 of 44 recent fetches
fully successful; is fetching working?
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1563#issuecomment-390822424
ok
1 - 100 of 4314 matches
Mail list logo
