Lofesa commented on issue #2038:
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/2038#issuecomment-784993379
Well... you can configure pagespeed to serve webp to all clients or not.
`pagespeed ServeRewrittenWebpUrlsToAnyAgent off;` that is the default.
When this
Poseidonas commented on issue #2038:
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/2038#issuecomment-784977780
> Hello,
>
> It seems like Safari 14 will support webp.
>
> The Safari 14 Beta release note :
>
>
Lofesa commented on issue #1729:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1729#issuecomment-784167785
> [This is a gist with the output from `?PageSpeedFilters=+debug`
](https://gist.github.com/benjaminadk/205e5fae50cfe54ea9ad2af73f3c8268)
>
No, this gist
benjaminadk edited a comment on issue #1729:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1729#issuecomment-784135494
I am back trying to get our server up again.
[This is a gist with the output from `?PageSpeedFilters=+debug`
benjaminadk commented on issue #1729:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1729#issuecomment-784135494
I am back trying to get our server up again.
[This is a gist with the output from `?PageSpeedFilters=+debug`
kinglozzer commented on issue #1237:
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/1237#issuecomment-783407078
This still appears to be an issue on Apache 2.4.29 / Pagespeed 1.13.35.2-0.
I’ll try to find time to test 1.14.36.1 soon
palviggi-flagbit opened a new issue #1731:
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1731
The long version of -b is broken, before using it, it checks for `buildir`
(with a missing d), so it says unrecognized option.
michacassola opened a new issue #1730:
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1730
Hi, please move the latest label to the actual latest stable release.
This is an automated message from the Apache Git
Lofesa commented on issue #1729:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1729#issuecomment-779804889
When you cleared the cache, css files are served rewrited by pagespeed or
are the original css files?
My bet is that some thing has changed and pagespeed is
benjaminadk commented on issue #1729:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1729#issuecomment-779779905
It seemed to be working for a while tonight. CSS files were all being
delivered. All I did was purge the cache a few times. Then I was switching
between Google
Lofesa edited a comment on issue #1729:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1729#issuecomment-779405993
| I did not set this up initially, and this is my intro to pagespeed. Any
ideas of what I am missing here?
Before this, you do nothing with css files?
Lofesa commented on issue #1729:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1729#issuecomment-779405993
| I did not set this up initially, and this is my intro to pagespeed. Any
ideas of what I am missing here?
Before this, you do nothing with css files?
oschaaf commented on issue #1729:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1729#issuecomment-779336742
Maybe the dns resolution is being cached for the domain on the server. The
module would then attempt to fetch from the old server.
benjaminadk opened a new issue #1729:
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1729
I had to rebuild a server and changed IPs but same domain. When I fire up
new server everything works except 404 for all pagespeed CSS files.
Other file types appear to be
wafedsf5 closed issue #1728:
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1728
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
wafedsf5 commented on issue #1728:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1728#issuecomment-775901434
The issue was fixed, this issue seems like using proxy protocol on HTTPS://
level, to fix this issue just needed to add
`proxy_set_header Accept-Encoding
wafedsf5 removed a comment on issue #1728:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1728#issuecomment-775875870
I found out that pagespeed is not working on HTTPS:// (only on HTTP://), I'm
using Nginx as a reverse proxy and I have no idea how to make pagespeed work
wafedsf5 commented on issue #1728:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1728#issuecomment-775875870
I found out that pagespeed is not working on HTTPS:// (only on HTTP://), I'm
using Nginx as a reverse proxy and I have no idea how to make pagespeed work
with
wafedsf5 opened a new issue #1728:
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1728
Good night programmers, I've been having a problem with pagespeed for some
time now, which led me to disable it in the past, but at the moment I really
wanted to solve the problem and
Lofesa edited a comment on issue #1726:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1726#issuecomment-773859432
This is an automated message from the Apache Git Service.
To respond to the message, please
Lofesa commented on issue #1726:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1726#issuecomment-773859432
Hace you searchhed for this same issue?
Read #1656
This is an automated message from the Apache
Lofesa commented on issue #1726:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1726#issuecomment-773859432
Hace you searchhed for this same issue?
Read #1656
This is an automated message from the Apache
eric-mathison opened a new issue #1726:
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1726
According to the Release notes, the version should be 1.14.36.1. But when
getting the URL:
```
https://github.com/apache/incubator-pagespeed-ngx/archive/v1.14.36.1.tar.gz
bantilan edited a comment on issue #1717:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1717#issuecomment-772481502
Got the same error on Ubuntu 20.10 (groovy), GCC 10.2.0:
```
-Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -pie -ldl
-lpthread
bantilan commented on issue #1717:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1717#issuecomment-772481502
Got the same error on Ubuntu 20.10 (groovy):
```
-Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -pie -ldl
-lpthread -lpthread -lcrypt
Lofesa commented on issue #2059:
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/2059#issuecomment-770427240
You can post this on core web vitals (Ligthouse) here
https://github.com/GoogleChrome/Lighthouse/issues
zz9pzza edited a comment on issue #1380:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1380#issuecomment-770401379
I bumped the number from
```
61c61
< fcntl(pipe_write_fd_, F_SETPIPE_SZ, 1024*1024 /* minimal amount of
bytes */);
---
>
zz9pzza commented on issue #1380:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1380#issuecomment-770401379
I bumped the number from
```
61c61
< fcntl(pipe_write_fd_, F_SETPIPE_SZ, 1024*1024 /* minimal amount of
bytes */);
---
>
kriskhunthong opened a new issue #2059:
URL: https://github.com/apache/incubator-pagespeed-mod/issues/2059
ในช่วงระยะเวลาการรวบรวม 28
วันที่ผ่านมาประสบการณ์โดยรวมของเพจทั้งหมดที่ให้บริการจากจุดเริ่มต้นนี้ไม่ผ่านการประเมินCore
Web Vitals
oschaaf closed issue #2058:
URL: https://github.com/apache/incubator-pagespeed-mod/issues/2058
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
oschaaf commented on issue #2058:
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/2058#issuecomment-770285949
Great, no problem. Closing this issue.
This is an automated message from the Apache Git Service.
To
jk2625 commented on issue #2058:
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/2058#issuecomment-770275125
Turns out tinkering with the compression level helped a whole lot. Totally
blew past me this morning.
Oddly enough, any brotli compression level below 10 had
oschaaf commented on issue #2058:
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/2058#issuecomment-770261883
I don't have it on top of mind, but I think it is worth investigating the
`FlushHtml` options and directives around that. The buffering by PageSpeed may
hurt a
jk2625 opened a new issue #2058:
URL: https://github.com/apache/incubator-pagespeed-mod/issues/2058
We're seeing issues (across multiple websites with different content) with
ModPagespeed v1.13.35.2-0 on Apache/2.4.6 causing significant TTFB delays
(~600-700ms in total) on websites with
kriskhunthong opened a new issue #2057:
URL: https://github.com/apache/incubator-pagespeed-mod/issues/2057
สวัสดีครับ ก่อนอื่นต้องบอกว่า มือใหม่มากๆ อยากรบกวนผู้มีประสบการณ์แนะนำ หรือ
แก้ไข หน้าเว็บไซต์[ ]( https://medhubnews.com/ )
ซึ่งมีปัญหา หน้าเว็บไซต์ ไม่ผ่านการประเมิน Core
Lofesa commented on issue #1720:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1720#issuecomment-766614357
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
uhlhosting commented on issue #1720:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1720#issuecomment-766492829
This is an automated message from the Apache Git Service.
To respond to the message, please log
Lofesa commented on issue #1720:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1720#issuecomment-766984205
1.- You have this html code:
```
https://uhl.site/; />
uhlhosting commented on issue #1720:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1720#issuecomment-766888678
@Lofesa I believe this is the way Pagespeed inlines the css if its in
header... This is purely done by pagespeed. Maybe it can be more investigated
and a bug
Lofesa commented on issue #1720:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1720#issuecomment-766614357
I have tested https://uhl.site in chrome browser and in webpagetest and
can´t see any outgoing connection to www.pagespeed-com.com, only uhl.site and
stats.uhl.site
uhlhosting commented on issue #1720:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1720#issuecomment-766492829
@Lofesa I am also testing CSP with pagespeed and it seems that there is some
external ongoing connection to www.pagespeed-mod.com ! ? Any idea what would
Lofesa commented on issue #2056:
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/2056#issuecomment-765274057
You have deleted the comment, but:
For disable inline_javascript:
ModPagespeedDisableFilters inline_javascript
ModPagespeedForbidFilters inline_javascript
applibs removed a comment on issue #2056:
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/2056#issuecomment-765240672
And how?
```
# DisableFilters inline_javascript
# pagespeed DisableFilters inline_javascript
```
I got error 500 with any of
applibs edited a comment on issue #2056:
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/2056#issuecomment-765240672
And how?
```
# DisableFilters inline_javascript
# pagespeed DisableFilters inline_javascript
```
I got error 500 with any of
applibs commented on issue #2056:
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/2056#issuecomment-765240672
And how?
# DisableFilters inline_javascript
# pagespeed DisableFilters inline_javascript
I got error 500 with any of this exmple.
Lofesa commented on issue #2056:
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/2056#issuecomment-765206359
Disable the inline_javascript filter or increase the size for javascript be
inlined or exclude jquery from pagespeed
applibs opened a new issue #2056:
URL: https://github.com/apache/incubator-pagespeed-mod/issues/2056
This version X-Mod-Pagespeed: 1.13.35.2-0 broken order processing
javascripts.
Some my files are like:
but it will generate:
//
uhlhosting commented on issue #1720:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1720#issuecomment-764584964
This is an automated message from the Apache Git Service.
To respond to the message, please log
uhlhosting edited a comment on issue #1720:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1720#issuecomment-764669858
@Lofesa not sure why this is now happening it seems somehow pagespeed
ignored my variables:
# WordPress-specific configurations, change according to
zz9pzza commented on issue #1380:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1380#issuecomment-764849749
Would just raising the number in
https://github.com/apache/incubator-pagespeed-ngx/blob/master/src/ngx_event_connection.cc#L64
help ( not as a solution for everyone
oschaaf commented on issue #1154:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1154#issuecomment-764917092
This is an automated message from the Apache Git Service.
To respond to the message, please log on
oschaaf commented on issue #1380:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1380#issuecomment-764916163
> Would just raising the number in
https://github.com/apache/incubator-pagespeed-ngx/blob/master/src/ngx_event_connection.cc#L64
help ( not as a solution for
oschaaf edited a comment on issue #1154:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1154#issuecomment-765012045
This is an automated message from the Apache Git Service.
To respond to the message, please
Lofesa commented on issue #1720:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1720#issuecomment-764834069
These are just regex expresions:
pagespeed Disallow "/wp-includes/js/dist/.js"; Thsi don´t macht this
vphantom commented on issue #1154:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1154#issuecomment-764856757
This is an automated message from the Apache Git Service.
To respond to the message, please log on
oschaaf edited a comment on issue #1380:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1380#issuecomment-764916163
> Would just raising the number in
https://github.com/apache/incubator-pagespeed-ngx/blob/master/src/ngx_event_connection.cc#L64
help ( not as a solution for
Lofesa edited a comment on issue #1720:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1720#issuecomment-764834069
These are just regex expressions:
This `pagespeed Disallow "/wp-includes/js/dist/.js";` don´t macht this
oschaaf edited a comment on issue #1154:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1154#issuecomment-765012045
That's one way to solve the problem :-) Now if you could configure
thenreverse proxy to cache .pagespeed. resources, you might actually get
something else
oschaaf edited a comment on issue #1154:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1154#issuecomment-765012045
That's one way to solve the problem :-) Now if you could configure
thenreverse proxy to cache .pagespeed. resources, you might actually get
something else
oschaaf commented on issue #1154:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1154#issuecomment-765012045
That's one way to solve the problem :-) Now if you could configure reverse
proxy to cache .pagespeed. resources, you might actually get something else out
of it
vphantom commented on issue #1154:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1154#issuecomment-764962790
I tested it with plain image URLs when pagespeed is on. My work-around for
now (which turned out to work quite well) is to have Nginx proxy into itself to
a
oschaaf commented on issue #1154:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1154#issuecomment-764917092
> Does nobody else in production need to set any header in Nginx?
That does seem unlikely to me. Does this happen only with `.pagespeed.`
rewritten urls?
oschaaf edited a comment on issue #1380:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1380#issuecomment-764916163
> Would just raising the number in
https://github.com/apache/incubator-pagespeed-ngx/blob/master/src/ngx_event_connection.cc#L64
help ( not as a solution for
oschaaf commented on issue #1380:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1380#issuecomment-764916163
> Would just raising the number in
https://github.com/apache/incubator-pagespeed-ngx/blob/master/src/ngx_event_connection.cc#L64
help ( not as a solution for
vphantom commented on issue #1154:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1154#issuecomment-764856757
I just dug a little deeper and actually ngx_pagespeed is removing all our
custom headers from our responses, both those set with `add_header` and
zz9pzza commented on issue #1380:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1380#issuecomment-764849749
Would just raising the number in
https://github.com/apache/incubator-pagespeed-ngx/blob/master/src/ngx_event_connection.cc#L64
help ( not as a solution for everyone
Lofesa edited a comment on issue #1720:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1720#issuecomment-764834069
These are just regex expressions:
This `pagespeed Disallow "/wp-includes/js/dist/.js";` don´t macht this
Lofesa commented on issue #1720:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1720#issuecomment-764834069
These are just regex expresions:
pagespeed Disallow "/wp-includes/js/dist/.js"; Thsi don´t macht this
uhlhosting edited a comment on issue #1720:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1720#issuecomment-764669858
@Lofesa not sure why this is now happening it seems somehow pagespeed
ignored my variables:
# WordPress-specific configurations, change according to
uhlhosting commented on issue #1720:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1720#issuecomment-764669858
@Lofesa not sure why this is now happening it seems somehow pagespeed
ignored my variables:
# WordPress-specific configurations, change according to your
uhlhosting commented on issue #1720:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1720#issuecomment-764584964
No that line is in another file thats called in nginx.conf.
In nginx conf i have normal gzip on; and brotli on;
oschaaf closed issue #2055:
URL: https://github.com/apache/incubator-pagespeed-mod/issues/2055
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
oschaaf commented on issue #2055:
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/2055#issuecomment-763530549
Closing this, you either need to follow up on the implied suggestion of the
message, or ensure faster (disk) i/o. Using memcached or larger caches for
pagespeed may
ashishkpal commented on issue #2055:
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/2055#issuecomment-763528419
mine question is should i worry about this error and if yes then how do i
configure SlowFileLatencyUs
oschaaf commented on issue #2055:
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/2055#issuecomment-763512642
Sure, but what is your question? :-)
This is an automated message from the Apache Git Service.
To
ashishkpal opened a new issue #2055:
URL: https://github.com/apache/incubator-pagespeed-mod/issues/2055
i am getting the below error on the nginx error log file
2021/01/20 10:32:29 [error] 1305#1305: [ngx_pagespeed 1.13.35.2-0] Slow
ReadFile operation on file
oschaaf commented on issue #1380:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1380#issuecomment-763210833
@zz9pzza seems relevant to this issue, sure. Apparently the tweak to bump
the buffer sizes associated to the pipe didn't help in your case, so it sounds
like a
zz9pzza commented on issue #1380:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1380#issuecomment-763210325
```
james_@DESKTOP-OTOBGUP:~$ curl -I https://archiveofourown.org/
HTTP/2 200
server: nginx/1.19.6
x-page-speed: 1.13.35.2-0
```
We are
urifoox commented on issue #1380:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1380#issuecomment-763207206
@zz9pzza - did you try to apply the patch / recompile?
https://github.com/apache/incubator-pagespeed-ngx/pull/1481
zz9pzza commented on issue #1380:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1380#issuecomment-763202036
I am hitting this we think.
http://mailman.nginx.org/pipermail/nginx/2021-January/060344.html
Lofesa commented on issue #1720:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1720#issuecomment-761824925
Line 18 is `pagespeed FetchWithGzip on;`?
You don´t need this as far as the resource request is not on other server,
no wired traffic between original resource and
uhlhosting commented on issue #1720:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1720#issuecomment-761818630
Pagespeed latest stable, and nginx 1.19.6 .
I did restarted yet it will reappear the message.
Yes gzip is on, yet there is the option to fetch with Gzip
Lofesa commented on issue #1720:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1720#issuecomment-761697667
What pagespeed/nginx version have you?
These messages are in a nginx reload? do a nginx restart a see what happens.
Line 18 of nginx.con is gzip on;?
hycday closed issue #2054:
URL: https://github.com/apache/incubator-pagespeed-mod/issues/2054
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
hycday edited a comment on issue #2054:
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/2054#issuecomment-761696705
oh wow, you are right !
images that are loaded once i press the "load more" button (hence, via
ajax), have the filename unchanged (unlike the first ones
hycday edited a comment on issue #2054:
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/2054#issuecomment-761696705
This is an automated message from the Apache Git Service.
To respond to the message, please
hycday commented on issue #2054:
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/2054#issuecomment-761696705
oh wow, you are right !
images that are loaded once i press the "load more" button (hence, via
ajax), have the filename unchanged (unlike the first ones who have
Lofesa commented on issue #2054:
URL:
https://github.com/apache/incubator-pagespeed-mod/issues/2054#issuecomment-761695959
Hi
Maybe these images are loaded by javascript, and then not processed by
pagespeed module... unless by IPRO.
Images optimized by IPRO don´t change the url or
hycday opened a new issue #2054:
URL: https://github.com/apache/incubator-pagespeed-mod/issues/2054
Hi,
I am using pagespeed with Apache, and I enabled the
"InPlaceResourceOptimization" option.
I have, on my wordpress, a gallery.
When loading the page, few first images appear,
uhlhosting commented on issue #1720:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1720#issuecomment-761560358
@Lofesa
I am keep receiving in nginx console these:
2021/01/16 13:58:25 [warn] 445981#445981: pagespeed: cannot set gzip,
command not found in
vphantom commented on issue #1154:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1154#issuecomment-761109267
My main use for it would've been to restore mod_headers_more's ability to
suppress Nginx's native `Server:` header. I guess I'm one of very few people
who care to
oschaaf commented on issue #1154:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1154#issuecomment-760537852
I remember that the POSITION_AUX feature didn't seem to get any traction or
testing feedback, or at least the large majority users didn't seem to need it.
The plan
zamanuhina commented on pull request #1617:
URL:
https://github.com/apache/incubator-pagespeed-ngx/pull/1617#issuecomment-760514480
>
>
> I have a docker image working and always updated with the latest nginx
mainline (1.7.3), openssl 1.1.1x and the latest pagespeed.
>
>
vphantom edited a comment on issue #1154:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1154#issuecomment-760313068
I can confirm this with Nginx 1.19.6 as well: adding `POSITION_AUX=true` to
the build environment causes the resulting binary to go into an endless loop
vphantom commented on issue #1154:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1154#issuecomment-760313068
I can confirm this with Nginx 1.19.6 as well: adding `POSITION_AUX=true` to
the build environment causes the resulting binary to go into an endless loop
when
uhlhosting commented on issue #1720:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1720#issuecomment-758648117
Need to check documentation for log level , for now havent seen anything to
change this within my settings.
Lofesa commented on issue #1563:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1563#issuecomment-758567612
As stated by @oschaaf the pagespeed module is unable to fecht the resource.
Maybe you have misconfigured https fechting or maybe you have a name
resolution
Lofesa commented on issue #1720:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1720#issuecomment-758557794
That´s normal log.
These url, like any other url for a wordpress post or page, is not a file,
and pagespeed can´t cache the url, so it tread to optimize with IPRO
oschaaf commented on issue #1563:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1563#issuecomment-758544457
> i am observing the below logs on mine nginx error. can anybody please help
me to resolve this issue
>
> 2021/01/12 09:24:56 [error] 2566#2586:
ashishkpal commented on issue #1563:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1563#issuecomment-758530634
i am observing the below logs on mine nginx error. can anybody please help
me to resolve this issue
2021/01/12 09:24:56 [error] 2566#2586: [ngx_pagespeed
801 - 900 of 4314 matches
Mail list logo
