[GitHub] [incubator-pagespeed-mod] Lofesa commented on issue #2038: Safari 14 will support webp
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 parameter is off, pagespeed only serve webp images to those browser that send a navigational header image/webp. If the browser don´t send ths header, no webp is served. I don´t know how Safari does this. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-mod] Poseidonas commented on issue #2038: Safari 14 will support webp
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 : > > https://developer.apple.com/documentation/safari-release-notes/safari-14-beta-release-notes > > ``` > Media > New Features > Added WebP image support. > ``` > > Thanks, > > Eric Great news! @Lofesa The pagespeed can server webp to any client but the problem is that the Safari cannot read webp. In other words you have to enable the UserAgent Append to ensure that your users can see your webp content successfully --as jpeg ofc and NOT as webp. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] Lofesa commented on issue #1729: Changed IP then CSS files 404
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 contains only javascript, in not the output from the filter. Some server config is wrong, when I try to PageSpeedFilters=+debug,-inline_css this come in an infinyte loop, the plus sign is decoded to %20 The outpu from the debug filter is some like:  You can see in green the debug messages. An other question is that some css don´t be manipulated by pagespeed. Ths one is:  But this other not:  See the diff betwen the Etag headers, and the second image don´t have the pagespeed header. Both are from your domain, so are authorized. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] benjaminadk edited a comment on issue #1729: Changed IP then CSS files 404
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` ](https://gist.github.com/benjaminadk/205e5fae50cfe54ea9ad2af73f3c8268) The configuration  PageSpeed appears to be partially working, with a couple CSS files not being found  When I purge the cache: That initial reload looks fine as it is fetching the actual server resources. Then subsequent reloads w/o purging is almost like a crap shoot - sometimes all the CSS files are available, and other times some are 404 - and it is different files each time. Once in a while it is the main CSS file, which is catastrophic. It also looked like a couple of the 404s were erroring around the Google Analytics script, even though they were totally unrelated style files. The configuration is exactly the same on this new server as the current one. This new one has new versions of Ubuntu, PHP, Nginx, etc. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] benjaminadk commented on issue #1729: Changed IP then CSS files 404
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` ](https://gist.github.com/benjaminadk/205e5fae50cfe54ea9ad2af73f3c8268) The configuration  PageSpeed appears to be partially working, with a couple CSS files not being found  When I purge the cache: That initial reload looks fine as it is fetching the actual server resources. Then subsequent reloads w/o purging is almost like a crap shoot - sometimes all the CSS files are available, and other times some are 404 - and it is different files each time. Once in a while it is the main CSS file, which is catastrophic. The configuration is exactly the same on this new server as the current one. This new one has new versions of Ubuntu, PHP, Nginx, etc. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-mod] kinglozzer commented on issue #1237: Headers removed when the response body is empty
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 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] palviggi-flagbit opened a new issue #1731: Long option --builddir doesn't work
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. https://github.com/apache/incubator-pagespeed-ngx/blob/master/scripts/build_ngx_pagespeed.sh#L316 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] michacassola opened a new issue #1730: "Latest" label on very old release
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 Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] Lofesa commented on issue #1729: Changed IP then CSS files 404
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 unable to fech the resources. I you try `https;//mydomain.com/?PageSpeedFilters=+debug` maybe the debug messages (as html comments in the code) have some clue. How pagespeed fecht https resources (What config have)? What domains have you authorized? Have you tried the LoadFromFile? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] benjaminadk commented on issue #1729: Changed IP then CSS files 404
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 users (chrome instances) and then all CSS 404ed again.
Could it have something to do with this session cookie?
```
#this next part requires the more_clear_headers module - if nginx fails,
remove this
if ($skip_cache = 0 ) {
more_clear_headers "Set-Cookie*";
set $rt_session "";
}
```
This is the only thing I didn't install from the previous setup. Based on
the comment I found I just skipped it.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] Lofesa edited a comment on issue #1729: Changed IP then CSS files 404
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? Can you try `https;//mydomain.com/?PageSpeedFilters=+debug` and then look at the html code to see debug messages? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] Lofesa commented on issue #1729: Changed IP then CSS files 404
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? Can you try `https;//mydomain.com/?PageSpeedFilters=+debug` anf then look at the html code to see debug messages? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] oschaaf commented on issue #1729: Changed IP then CSS files 404
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. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] benjaminadk opened a new issue #1729: Changed IP then CSS files 404
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 working as expected, and when I try `?ModPagespeed=off` it fetches the correct file directly and everything looks fine. Running the same CSS related stuff as old configuration ``` #CSS handling pagespeed EnableFilters combine_css,fallback_rewrite_css_urls,flatten_css_imports,inline_css,rewrite_css; ``` I did not set this up initially, and this is my intro to pagespeed. Any ideas of what I am missing here? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] wafedsf5 closed issue #1728: Nginx - Pagespeed & Static Content Issue
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 above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] wafedsf5 commented on issue #1728: Nginx - Pagespeed & Static Content Issue
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 "gzip";` on the location resource This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] wafedsf5 removed a comment on issue #1728: Nginx - Pagespeed & Static Content Issue
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 with HTTPS://, anyone can help? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] wafedsf5 commented on issue #1728: Nginx - Pagespeed & Static Content Issue
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 HTTPS://, anyone can help? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] wafedsf5 opened a new issue #1728: Nginx - Pagespeed & Static Content Issue
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 start using pagespeed.
To try to explain the problem, when I'm using pagespeed all the static
content becomes unreadable, and I can give you some example on a CSS file:
Without pagespeed: https://i.imgur.com/qgmZeER.png With pagespeed:
https://i.imgur.com/o9oLeCi.png This happens in CSS & JS.
I tried to default configurations that I found on the internet, my own
configurations, disabling each setting... Nothing seems to work, I'm using
nginx as Reverse Proxy, and connections are being passed with proxy_pass Nginx
version: OpenResty 1.19.3.1 PageSpeed version: v1.13.35.2-stable PSOL is also
configured for the v1.13.35.2 version.
Server Block:
Pagespeed configurations
Server block:
```
pagespeed on;
pagespeed RewriteLevel OptimizeForBandwidth;
location ~ "\.pagespeed\.([a-z]\.)?[a-z]{2}\.[^.]{10}\.[^.]+" {
add_header "" "";
}
location ~ "^/pagespeed_static/" { }
location ~ "^/ngx_pagespeed_beacon$" { }
## PageSpeed Cache Purge
pagespeed EnableCachePurge on;
pagespeed PurgeMethod PURGE;
pagespeed DownstreamCacheRewrittenPercentageThreshold 95;
## Minify
pagespeed EnableFilters combine_heads;
pagespeed EnableFilters collapse_whitespace;
pagespeed EnableFilters convert_meta_tags;
pagespeed EnableFilters elide_attributes;
pagespeed EnableFilters pedantic;
pagespeed EnableFilters remove_comments;
pagespeed EnableFilters remove_quotes;
pagespeed EnableFilters trim_urls;
pagespeed EnableFilters outline_css;
pagespeed EnableFilters combine_css;
pagespeed EnableFilters inline_import_to_link;
pagespeed EnableFilters inline_css;
pagespeed EnableFilters inline_google_font_css;
pagespeed EnableFilters move_css_above_scripts;
pagespeed EnableFilters move_css_to_head;
pagespeed EnableFilters prioritize_critical_css;
pagespeed EnableFilters rewrite_css;
pagespeed EnableFilters fallback_rewrite_css_urls;
pagespeed EnableFilters rewrite_style_attributes_with_url;
pagespeed EnableFilters combine_javascript;
pagespeed EnableFilters canonicalize_javascript_libraries;
pagespeed EnableFilters inline_javascript;
## Speed-up
pagespeed EnableFilters dedup_inlined_images;
pagespeed EnableFilters inline_preview_images;
pagespeed EnableFilters resize_mobile_images;
pagespeed EnableFilters lazyload_images;
pagespeed EnableFilters inline_images;
pagespeed EnableFilters convert_gif_to_png;
pagespeed EnableFilters convert_jpeg_to_progressive;
pagespeed EnableFilters recompress_jpeg;
pagespeed EnableFilters recompress_png;
pagespeed EnableFilters recompress_webp;
pagespeed EnableFilters strip_image_color_profile;
pagespeed EnableFilters strip_image_meta_data;
pagespeed EnableFilters jpeg_subsampling;
pagespeed EnableFilters convert_png_to_jpeg;
pagespeed EnableFilters resize_images;
pagespeed EnableFilters resize_rendered_image_dimensions;
pagespeed EnableFilters convert_jpeg_to_webp;
pagespeed EnableFilters convert_to_webp_lossless;
pagespeed EnableFilters insert_image_dimensions;
pagespeed NoTransformOptimizedImages on;
pagespeed EnableFilters sprite_images;
```
HTTP block:
```
pagespeed RespectVary off;
pagespeed ProcessScriptVariables on;
pagespeed FetchWithGzip on;
pagespeed DisableRewriteOnNoTransform off;
pagespeed SupportNoScriptEnabled false;
pagespeed ModifyCachingHeaders on;
pagespeed MaxCacheableContentLength -1;
pagespeed FileCachePath /ramdisk/nginx/cache/ngx_pagespeed/;
pagespeed FileCacheSizeKb102400;
pagespeed FileCacheCleanIntervalMs 360;
pagespeed FileCacheInodeLimit50;
pagespeed LRUCacheKbPerProcess 1024;
pagespeed LRUCacheByteLimit16384;
pagespeed MemcachedThreads 8;
pagespeed MemcachedServers "localhost:11211";
```
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] Lofesa edited a comment on issue #1726: What is the latest build release for nginx?
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 log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] Lofesa commented on issue #1726: What is the latest build release for nginx?
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 Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] Lofesa commented on issue #1726: What is the latest build release for nginx?
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 Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] eric-mathison opened a new issue #1726: What is the latest build release for nginx?
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 ``` it resolves with a 404. What version is recommended to use? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] bantilan edited a comment on issue #1717: Could not complete the build
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 -lpthread -lcrypt /root/nginx-1.19.6/debian/modules/ngx_pagespeed/psol/lib/Release/linux/x64/pagespeed_automatic.a -lstdc++ -lrt -pthread -lm -luuid -lm -lpcre -lssl -lcrypto -ldl -lpthread -lz \ -Wl,-E /usr/bin/ld: /root/nginx-1.19.6/debian/modules/ngx_pagespeed/psol/lib/Release/linux/x64/pagespeed_automatic.a(107.signals.o.o): in function `pagespeed_ol_apr_signal_description_get': signals.c:(.text.apr_signal_description_get+0xe): undefined reference to `sys_siglist' collect2: error: ld returned 1 exit status make[2]: *** [objs/Makefile:397: objs/nginx] Error 1 make[2]: Leaving directory '/root/nginx-1.19.6/debian/build-nginx' make[1]: *** [Makefile:8: build] Error 2 make[1]: Leaving directory '/root/nginx-1.19.6/debian/build-nginx' make: *** [debian/rules:52: build-arch.nginx] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 ``` This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] bantilan commented on issue #1717: Could not complete the build
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 /root/nginx-1.19.6/debian/modules/ngx_pagespeed/psol/lib/Release/linux/x64/pagespeed_automatic.a -lstdc++ -lrt -pthread -lm -luuid -lm -lpcre -lssl -lcrypto -ldl -lpthread -lz \ -Wl,-E /usr/bin/ld: /root/nginx-1.19.6/debian/modules/ngx_pagespeed/psol/lib/Release/linux/x64/pagespeed_automatic.a(107.signals.o.o): in function `pagespeed_ol_apr_signal_description_get': signals.c:(.text.apr_signal_description_get+0xe): undefined reference to `sys_siglist' collect2: error: ld returned 1 exit status make[2]: *** [objs/Makefile:397: objs/nginx] Error 1 make[2]: Leaving directory '/root/nginx-1.19.6/debian/build-nginx' make[1]: *** [Makefile:8: build] Error 2 make[1]: Leaving directory '/root/nginx-1.19.6/debian/build-nginx' make: *** [debian/rules:52: build-arch.nginx] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 ``` This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-mod] Lofesa commented on issue #2059: 28 วันที่ผ่านมาประสบการณ์โดยรวมของเพจทั้งหมดที่ให้บริการจากจุดเริ่มต้นนี้ไม่ผ่านการประเมิน Core Web Vitals
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 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] zz9pzza edited a comment on issue #1380: nginx worker 100% cpu usage (spinning on write returning EAGAIN)
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 */); --- > fcntl(pipe_write_fd_, F_SETPIPE_SZ, 200*1024 /* minimal amount of bytes */); ``` And over 4 servers with 200 we had the 17 times on a day with 57 millon page views. the next week was 58 million and the same servers with the new code hit the issue 6 times. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] zz9pzza commented on issue #1380: nginx worker 100% cpu usage (spinning on write returning EAGAIN)
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 */); --- > fcntl(pipe_write_fd_, F_SETPIPE_SZ, 200*1024 /* minimal amount of bytes */); ``` And over 4 servers with 200 we had the 17 times on a day with 57 millon page views. the next week was 58 million and the same servers with the new code hit the isse 6 times. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-mod] kriskhunthong opened a new issue #2059: ในช่วงระยะเวลาการรวบรวม 28 วันที่ผ่านมาประสบการณ์โดยรวมของเพจทั้งหมดที่ให้บริการจากจุดเริ่มต้นนี้ไม่ผ่านการประเมินCore Web Vi
kriskhunthong opened a new issue #2059: URL: https://github.com/apache/incubator-pagespeed-mod/issues/2059 ในช่วงระยะเวลาการรวบรวม 28 วันที่ผ่านมาประสบการณ์โดยรวมของเพจทั้งหมดที่ให้บริการจากจุดเริ่มต้นนี้ไม่ผ่านการประเมินCore Web Vitals หากต้องการดูคำแนะนำที่ปรับให้เหมาะกับแต่ละหน้าให้วิเคราะห์ [URL ของแต่ละหน้า](https://medhubnews.com/) เช่น การเปลี่ยนแปลงเค้าโครงสะสม คริษฐ์ ขันทอง This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-mod] oschaaf closed issue #2058: ModPagespeed Slow TTFB w/ Brotli Compression enabled on pages with more HTML
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 above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-mod] oschaaf commented on issue #2058: ModPagespeed Slow TTFB w/ Brotli Compression enabled on pages with more HTML
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 respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-mod] jk2625 commented on issue #2058: ModPagespeed Slow TTFB w/ Brotli Compression enabled on pages with more HTML
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 very little impact on Pagespeed - using 10 or 11 caused the issue. I guess this makes sense given 10's a lot more aggressive. If anyone else encounters this issue - just lower your Brotli Compress level directive to 9 or so. It's not an issue on ngx_pagespeed either so that can also be used. Thanks @oschaaf This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-mod] oschaaf commented on issue #2058: ModPagespeed Slow TTFB w/ Brotli Compression enabled on pages with more HTML
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 little bit more when brotli runs in front of it. Of course, forcing PageSpeed to flush earlier may also result in lost optimization opportunities for that module, as it has to forego context of bytes that already on the wire, that in retrospect could have been rewritten in a better way as the module learns about what came next. Alternatively, don't apply brotli compression to the html or use a lower compression level for that. Maybe some experimenting will learn with what works best. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-mod] jk2625 opened a new issue #2058: ModPagespeed Slow TTFB w/ Brotli Compression enabled on pages with more HTML
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 somewhat larger HTML content (> 100kb or so). This only happens when: 1. ModPagespeed is turned on (disabling via ?ModPagespeed=off fixes this) 2. Brotli compression via mod_brotli is on and compressing the HTML Normal TTFB is roughly 100-200ms in total. This happens regardless of what filters are enabled - setting it to pass through and/or disabling all active filters still causes the same delay. ModPagespeedHttpCacheCompressionLevel 0 has been tried too. /var/cache/mod_pagespeed/v3 is currently 93M, /var/cache/mod_pagespeed/shm_metadata_cache is currently 5.3M Both are local filesystems - not using Memcache. Relevant configuration directives: ModPagespeedRewriteDeadlinePerFlushMs 10 ModPagespeedCreateSharedMemoryMetadataCache ~51M ModPagespeedFileCacheSizeKb 102400 ModPagespeedFileCacheCleanIntervalMs 360 ModPagespeedLRUCacheKbPerProcess 1024 ModPagespeedLRUCacheByteLimit16384 With debug: https://pastebin.com/EPBFa9hj #NumFlushes0 #EndDocument after 26133us #Total Parse duration 5849us #Total Render duration 1330us #Total Idle duration 20284us The following filters were disabled for this request: SupportNoscript No pagespeed errors in /var/log/httpd/error_log Happens on both PHP & static HTML files Kernel: 3.10.0-1160.11.1.el7.x86_64 CentOS 7 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-mod] kriskhunthong opened a new issue #2057: หน้าเว็บไซต์ ไม่ผ่านการประเมิน Core Web Vitals
kriskhunthong opened a new issue #2057: URL: https://github.com/apache/incubator-pagespeed-mod/issues/2057 สวัสดีครับ ก่อนอื่นต้องบอกว่า มือใหม่มากๆ อยากรบกวนผู้มีประสบการณ์แนะนำ หรือ แก้ไข หน้าเว็บไซต์[ ]( https://medhubnews.com/ ) ซึ่งมีปัญหา หน้าเว็บไซต์ ไม่ผ่านการประเมิน Core Web Vitals โปรดให้คำแนะนำกับเรา คริษฐ์ ขันทอง kris_n...@hotmail.com เจ้าของ เว็บไซต์ข่าวสาร [](https://medhubnews.com/) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] Lofesa commented on issue #1720: URL is not in cache
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 GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] uhlhosting commented on issue #1720: URL is not in cache
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 on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] Lofesa commented on issue #1720: URL is not in cache
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/; />
[GitHub] [incubator-pagespeed-ngx] uhlhosting commented on issue #1720: URL is not in cache
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 raised? 2.-You have 1 url (https://uhl.site) with 2 cannonicals (https://uhl.site and https://uhl.site/de). These is not the way to have multilingual pages. You need to explore the hreflang html labels. Can you elaborate a bit on this one? I can invite the developer of the plugin since this is very early alpha stage plugin for oxygen. @sbouey maybe you can check this? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] Lofesa commented on issue #1720: URL is not in cache
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 https://www.webpagetest.org/result/210125_DiT4_a0658f20d9b5e3aa0f60ee1b9c939dd8/ But you have some mistakes: 1.- All css inlined before the meta og and tewitter. This make Facebook and twitter don´t read these labels, the css must be inlined after these labels. 2.-You have 1 url (https://uhl.site) with 2 cannonicals (https://uhl.site and https://uhl.site/de). These is not the way to have multilingual pages. You need to explore the hreflang html labels. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] uhlhosting commented on issue #1720: URL is not in cache
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 pagespeed need to connect to external sources? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-mod] Lofesa commented on issue #2056: Broken javascript loading order
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 For increase/decrease the size of files inlined: ModPagespeedJsInlineMaxBytes bytes For exclude jquery: ModPagespeedDisallow *jquery.js* (a wildcar spec, like regex expression) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-mod] applibs removed a comment on issue #2056: Broken javascript loading order
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 this exmple. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-mod] applibs edited a comment on issue #2056: Broken javascript loading order
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 this exmple. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-mod] applibs commented on issue #2056: Broken javascript loading order
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. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-mod] Lofesa commented on issue #2056: Broken javascript loading order
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 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-mod] applibs opened a new issue #2056: Broken javascript loading order
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: // Its impossible because defer attribute by specification not work with inlined javascript. Soo, when I am using jQuery in my external-script-1.js my scripts is broken because "Uncaught ReferenceError: jQuery is not defined". Its because pagespeed ignore defer and moved to source code to
[GitHub] [incubator-pagespeed-ngx] uhlhosting commented on issue #1720: URL is not in cache
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 on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] uhlhosting edited a comment on issue #1720: URL is not in cache
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 your domain and installation path pagespeed Disallow */*.php*; pagespeed Disallow */checkout/*; pagespeed Disallow */status/*; pagespeed Disallow */opui/*; **pagespeed Disallow "*/wp-includes/js/dist/*.js"; pagespeed Disallow "*/wp-includes/js/tinymce/*.js"; pagespeed Disallow "*/wp-includes/js/jquery/jquery.js";** pagespeed Disallow "*/wp-content/plugins/oxygen/component-framework/vendor/*.js"; pagespeed Disallow "*/wp-content/cache/*.css"; pagespeed Disallow "*/admin-bar.min.css"; pagespeed Disallow "*/dashicons.min.css"; I specifically specified not to change those files, when I try to use the oxygen builder editor I get this: ``` [Thu, 21 Jan 2021 14:11:17 GMT] [Info] [2165570] Script https://uhl.site/wp-includes/js/dist/vendor/moment.min.js?ver=2.26.0 didn't shrink. [Thu, 21 Jan 2021 14:11:17 GMT] [Info] [2165570] ipro: CSS parser increased size of CSS file https://uhl.site/wp-content/plugins/piotnetforms-pro/assets/css/minify/admin.min.css?ver=1.0.69 by 57 bytes. [Thu, 21 Jan 2021 14:11:17 GMT] [Info] [2165570] ipro: Recompressing image `https://uhl.site/wp-includes/js/thickbox/loadingAnimation.gif' (15238 -> 15238 bytes) doesn't save space; dropped. [Thu, 21 Jan 2021 14:11:17 GMT] [Info] [2165570] ipro: Shrinking image `https://uhl.site/wp-content/plugins/falang/admin/img/icon-80x80.png' (4379 bytes) to `https://uhl.site/wp-content/plugins/falang/admin/img/xicon-80x80.png.pagespeed.ic.hN2wQBPvsU.png' (3805 bytes) [Thu, 21 Jan 2021 14:11:18 GMT] [Info] [2165565] Trying to serve rewritten resource in-place: https://stats.uhl.site/js/plausible.js [Thu, 21 Jan 2021 14:11:18 GMT] [Error] [2165570] [https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/image.svg:0] serf_context_run error status=111 (Connection refused) [Thu, 21 Jan 2021 14:11:18 GMT] [Warning] [2165570] Fetch failed to start: https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/image.svg [Thu, 21 Jan 2021 14:11:18 GMT] [Info] [2165570] HTTPCache key=https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/image.svg fragment=uhl.site: remembering recent failure for 299 seconds. [Thu, 21 Jan 2021 14:11:18 GMT] [Info] [2165570] HTTPCache key=https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/image.svg fragment=uhl.site: remembering recent failure for 299 seconds. [Thu, 21 Jan 2021 14:11:18 GMT] [Error] [2165570] [https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/image-active.svg:0] serf_context_run error status=111 (Connection refused) [Thu, 21 Jan 2021 14:11:18 GMT] [Warning] [2165570] Fetch failed to start: https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/image-active.svg [Thu, 21 Jan 2021 14:11:18 GMT] [Info] [2165570] HTTPCache key=https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/image-active.svg fragment=uhl.site: remembering recent failure for 299 seconds. [Thu, 21 Jan 2021 14:11:18 GMT] [Info] [2165570] HTTPCache key=https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/image-active.svg fragment=uhl.site: remembering recent failure for 299 seconds. [Thu, 21 Jan 2021 14:11:18 GMT] [Error] [2165570] [https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/gallery-active.svg:0] serf_context_run error status=111 (Connection refused) [Thu, 21 Jan 2021 14:11:18 GMT] [Warning] [2165570] Fetch failed to start: https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/gallery-active.svg [Thu, 21 Jan 2021 14:11:18 GMT] [Info] [2165570] HTTPCache key=https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/gallery-active.svg fragment=uhl.site: remembering recent failure for 299 seconds. [Thu, 21 Jan 2021 14:11:18 GMT] [Info] [2165570] HTTPCache key=https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/gallery-active.svg fragment=uhl.site: remembering recent failure for 299 seconds. [Thu, 21 Jan 2021 14:11:18 GMT] [Error] [2165570] [https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/modal.svg:0] serf_context_run error status=111 (Connection refused) [Thu, 21 Jan 2021 14:11:18 GMT] [Warning] [2165570] Fetch failed to start:
[GitHub] [incubator-pagespeed-ngx] zz9pzza commented on issue #1380: nginx worker 100% cpu usage (spinning on write returning EAGAIN)
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 just to make it less likely ) ? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] oschaaf commented on issue #1154: POSITION_AUX=true broken in nginx 1.9.11+
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 to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] oschaaf commented on issue #1380: nginx worker 100% cpu usage (spinning on write returning EAGAIN)
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 everyone just to make it less likely ) ? Well, it's worth trying, and the chance is probably trivial, but I wouldn't bet on it :( This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] oschaaf edited a comment on issue #1154: POSITION_AUX=true broken in nginx 1.9.11+
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 log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] Lofesa commented on issue #1720: URL is not in cache
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 https://uhl.site/wp-includes/js/dist/vendor/moment.min.js?ver=2.26 Maybe pagespeed Disallow "/wp-includes/js/dist/**\*.js\***"; this matcht. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] vphantom commented on issue #1154: POSITION_AUX=true broken in nginx 1.9.11+
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 to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] oschaaf edited a comment on issue #1380: nginx worker 100% cpu usage (spinning on write returning EAGAIN)
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 everyone just to make it less likely ) ? Well, it's worth trying, and the change is probably trivial, but I wouldn't bet on it :( This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] Lofesa edited a comment on issue #1720: URL is not in cache
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 `https://uhl.site/wp-includes/js/dist/vendor/moment.min.js?ver=2.26` Maybe `pagespeed Disallow "/wp-includes/js/dist/*.js*";` this matcht. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] oschaaf edited a comment on issue #1154: POSITION_AUX=true broken in nginx 1.9.11+
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 out of it too, and minimize the incurred overhead. (note caching the html is tempting, but harder to set up correctly, but just the `.pagespeed.` resources should be hassle-free). This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] oschaaf edited a comment on issue #1154: POSITION_AUX=true broken in nginx 1.9.11+
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 out of it too, and minimize the incurred overhead. (note caching the html is tempting, but harder to set up correctly, but just the .pagespeed. resources should be hassle-free). This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] oschaaf commented on issue #1154: POSITION_AUX=true broken in nginx 1.9.11+
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 too, and minimize the incurred overhead. (note caching the html is tempting, but harder to set up correctly, but just the .pagespeed. resources should be hassle-free). This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] vphantom commented on issue #1154: POSITION_AUX=true broken in nginx 1.9.11+
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 private port on the paths I want PageSpeed involved, so I can massage the headers before they go out. The inside server enables PageSpeed and the outside one doesn't. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] oschaaf commented on issue #1154: POSITION_AUX=true broken in nginx 1.9.11+
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? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] oschaaf edited a comment on issue #1380: nginx worker 100% cpu usage (spinning on write returning EAGAIN)
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 everyone just to make it less likely ) ? Well, it's worth trying, and the change is probably trivial, but I wouldn't bet on it :( This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] oschaaf commented on issue #1380: nginx worker 100% cpu usage (spinning on write returning EAGAIN)
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 everyone just to make it less likely ) ? Well, it's worth trying, and the chance is probably trivial, but I wouldn't bet on it :( This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] vphantom commented on issue #1154: POSITION_AUX=true broken in nginx 1.9.11+
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 `more_set_headers`. This means when PageSpeed is enabled we lose STS, Referrer-Policy, X-XSS-Protection, Allow and even the Set-Cookie emitted by ngx_http_userid. We also lose ETag and Cache-Control (which were overwritten anyway) with `ModifyCacheHeaders off`. I can't believe we hadn't noticed that before today… Does nobody else in production need to set any header in Nginx? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] zz9pzza commented on issue #1380: nginx worker 100% cpu usage (spinning on write returning EAGAIN)
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 just to make it less likely ) ? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] Lofesa edited a comment on issue #1720: URL is not in cache
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 `https://uhl.site/wp-includes/js/dist/vendor/moment.min.js?ver=2.26` Maybe `pagespeed Disallow "/wp-includes/js/dist/*.js*";` this matcht. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] Lofesa commented on issue #1720: URL is not in cache
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 https://uhl.site/wp-includes/js/dist/vendor/moment.min.js?ver=2.26 Maybe pagespeed Disallow "/wp-includes/js/dist/**\*.js\***"; this matcht. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] uhlhosting edited a comment on issue #1720: URL is not in cache
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 your domain and installation path pagespeed Disallow */*.php*; pagespeed Disallow */checkout/*; pagespeed Disallow */status/*; pagespeed Disallow */opui/*; **pagespeed Disallow "*/wp-includes/js/dist/*.js"; pagespeed Disallow "*/wp-includes/js/tinymce/*.js"; pagespeed Disallow "*/wp-includes/js/jquery/jquery.js";** pagespeed Disallow "*/wp-content/plugins/oxygen/component-framework/vendor/*.js"; pagespeed Disallow "*/wp-content/cache/*.css"; pagespeed Disallow "*/admin-bar.min.css"; pagespeed Disallow "*/dashicons.min.css"; I specifically specified not to change those files, when I try to use the oxygen builder editor I get this: ``` [Thu, 21 Jan 2021 14:11:17 GMT] [Info] [2165570] Script https://uhl.site/wp-includes/js/dist/vendor/moment.min.js?ver=2.26.0 didn't shrink. [Thu, 21 Jan 2021 14:11:17 GMT] [Info] [2165570] ipro: CSS parser increased size of CSS file https://uhl.site/wp-content/plugins/piotnetforms-pro/assets/css/minify/admin.min.css?ver=1.0.69 by 57 bytes. [Thu, 21 Jan 2021 14:11:17 GMT] [Info] [2165570] ipro: Recompressing image `https://uhl.site/wp-includes/js/thickbox/loadingAnimation.gif' (15238 -> 15238 bytes) doesn't save space; dropped. [Thu, 21 Jan 2021 14:11:17 GMT] [Info] [2165570] ipro: Shrinking image `https://uhl.site/wp-content/plugins/falang/admin/img/icon-80x80.png' (4379 bytes) to `https://uhl.site/wp-content/plugins/falang/admin/img/xicon-80x80.png.pagespeed.ic.hN2wQBPvsU.png' (3805 bytes) [Thu, 21 Jan 2021 14:11:18 GMT] [Info] [2165565] Trying to serve rewritten resource in-place: https://stats.uhl.site/js/plausible.js [Thu, 21 Jan 2021 14:11:18 GMT] [Error] [2165570] [https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/image.svg:0] serf_context_run error status=111 (Connection refused) [Thu, 21 Jan 2021 14:11:18 GMT] [Warning] [2165570] Fetch failed to start: https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/image.svg [Thu, 21 Jan 2021 14:11:18 GMT] [Info] [2165570] HTTPCache key=https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/image.svg fragment=uhl.site: remembering recent failure for 299 seconds. [Thu, 21 Jan 2021 14:11:18 GMT] [Info] [2165570] HTTPCache key=https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/image.svg fragment=uhl.site: remembering recent failure for 299 seconds. [Thu, 21 Jan 2021 14:11:18 GMT] [Error] [2165570] [https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/image-active.svg:0] serf_context_run error status=111 (Connection refused) [Thu, 21 Jan 2021 14:11:18 GMT] [Warning] [2165570] Fetch failed to start: https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/image-active.svg [Thu, 21 Jan 2021 14:11:18 GMT] [Info] [2165570] HTTPCache key=https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/image-active.svg fragment=uhl.site: remembering recent failure for 299 seconds. [Thu, 21 Jan 2021 14:11:18 GMT] [Info] [2165570] HTTPCache key=https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/image-active.svg fragment=uhl.site: remembering recent failure for 299 seconds. [Thu, 21 Jan 2021 14:11:18 GMT] [Error] [2165570] [https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/gallery-active.svg:0] serf_context_run error status=111 (Connection refused) [Thu, 21 Jan 2021 14:11:18 GMT] [Warning] [2165570] Fetch failed to start: https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/gallery-active.svg [Thu, 21 Jan 2021 14:11:18 GMT] [Info] [2165570] HTTPCache key=https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/gallery-active.svg fragment=uhl.site: remembering recent failure for 299 seconds. [Thu, 21 Jan 2021 14:11:18 GMT] [Info] [2165570] HTTPCache key=https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/gallery-active.svg fragment=uhl.site: remembering recent failure for 299 seconds. [Thu, 21 Jan 2021 14:11:18 GMT] [Error] [2165570] [https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/modal.svg:0] serf_context_run error status=111 (Connection refused) [Thu, 21 Jan 2021 14:11:18 GMT] [Warning] [2165570] Fetch failed to start:
[GitHub] [incubator-pagespeed-ngx] uhlhosting commented on issue #1720: URL is not in cache
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 domain and installation path pagespeed Disallow */*.php*; pagespeed Disallow */checkout/*; pagespeed Disallow */status/*; pagespeed Disallow */opui/*; **pagespeed Disallow "*/wp-includes/js/dist/*.js"; pagespeed Disallow "*/wp-includes/js/tinymce/*.js"; pagespeed Disallow "*/wp-includes/js/jquery/jquery.js";** pagespeed Disallow "*/wp-content/plugins/oxygen/component-framework/vendor/*.js"; pagespeed Disallow "*/wp-content/cache/*.css"; pagespeed Disallow "*/admin-bar.min.css"; pagespeed Disallow "*/dashicons.min.css"; I specifically specified not to change those files, when I try to use the oxygen builder editor I get this: [Thu, 21 Jan 2021 14:11:17 GMT] [Info] [2165570] Script https://uhl.site/wp-includes/js/dist/vendor/moment.min.js?ver=2.26.0 didn't shrink. [Thu, 21 Jan 2021 14:11:17 GMT] [Info] [2165570] ipro: CSS parser increased size of CSS file https://uhl.site/wp-content/plugins/piotnetforms-pro/assets/css/minify/admin.min.css?ver=1.0.69 by 57 bytes. [Thu, 21 Jan 2021 14:11:17 GMT] [Info] [2165570] ipro: Recompressing image `https://uhl.site/wp-includes/js/thickbox/loadingAnimation.gif' (15238 -> 15238 bytes) doesn't save space; dropped. [Thu, 21 Jan 2021 14:11:17 GMT] [Info] [2165570] ipro: Shrinking image `https://uhl.site/wp-content/plugins/falang/admin/img/icon-80x80.png' (4379 bytes) to `https://uhl.site/wp-content/plugins/falang/admin/img/xicon-80x80.png.pagespeed.ic.hN2wQBPvsU.png' (3805 bytes) [Thu, 21 Jan 2021 14:11:18 GMT] [Info] [2165565] Trying to serve rewritten resource in-place: https://stats.uhl.site/js/plausible.js [Thu, 21 Jan 2021 14:11:18 GMT] [Error] [2165570] [https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/image.svg:0] serf_context_run error status=111 (Connection refused) [Thu, 21 Jan 2021 14:11:18 GMT] [Warning] [2165570] Fetch failed to start: https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/image.svg [Thu, 21 Jan 2021 14:11:18 GMT] [Info] [2165570] HTTPCache key=https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/image.svg fragment=uhl.site: remembering recent failure for 299 seconds. [Thu, 21 Jan 2021 14:11:18 GMT] [Info] [2165570] HTTPCache key=https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/image.svg fragment=uhl.site: remembering recent failure for 299 seconds. [Thu, 21 Jan 2021 14:11:18 GMT] [Error] [2165570] [https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/image-active.svg:0] serf_context_run error status=111 (Connection refused) [Thu, 21 Jan 2021 14:11:18 GMT] [Warning] [2165570] Fetch failed to start: https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/image-active.svg [Thu, 21 Jan 2021 14:11:18 GMT] [Info] [2165570] HTTPCache key=https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/image-active.svg fragment=uhl.site: remembering recent failure for 299 seconds. [Thu, 21 Jan 2021 14:11:18 GMT] [Info] [2165570] HTTPCache key=https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/image-active.svg fragment=uhl.site: remembering recent failure for 299 seconds. [Thu, 21 Jan 2021 14:11:18 GMT] [Error] [2165570] [https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/gallery-active.svg:0] serf_context_run error status=111 (Connection refused) [Thu, 21 Jan 2021 14:11:18 GMT] [Warning] [2165570] Fetch failed to start: https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/gallery-active.svg [Thu, 21 Jan 2021 14:11:18 GMT] [Info] [2165570] HTTPCache key=https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/gallery-active.svg fragment=uhl.site: remembering recent failure for 299 seconds. [Thu, 21 Jan 2021 14:11:18 GMT] [Info] [2165570] HTTPCache key=https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/gallery-active.svg fragment=uhl.site: remembering recent failure for 299 seconds. [Thu, 21 Jan 2021 14:11:18 GMT] [Error] [2165570] [https://uhl.site/wp-content/plugins/oxygen/component-framework/toolbar/UI/oxygen-icons/add-icons/modal.svg:0] serf_context_run error status=111 (Connection refused) [Thu, 21 Jan 2021 14:11:18 GMT] [Warning] [2165570] Fetch failed to start:
[GitHub] [incubator-pagespeed-ngx] uhlhosting commented on issue #1720: URL is not in cache
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; This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-mod] oschaaf closed issue #2055: configure SlowFileLatencyUs to change threshold
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 above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-mod] oschaaf commented on issue #2055: configure SlowFileLatencyUs to change threshold
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 reduce disk pressure. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-mod] ashishkpal commented on issue #2055: configure SlowFileLatencyUs to change threshold
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 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-mod] oschaaf commented on issue #2055: configure SlowFileLatencyUs to change threshold
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 respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-mod] ashishkpal opened a new issue #2055: configure SlowFileLatencyUs to change threshold
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 /var/cache/ngx_pagespeed/v3/x/http,3A/,x,2Cqv=1.pagespeed.ic.i1sENDyBR7.png,: 120.302ms; configure SlowFileLatencyUs to change threshold This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] oschaaf commented on issue #1380: nginx worker 100% cpu usage (spinning on write returning EAGAIN)
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 proper fix for the TODO over at https://github.com/apache/incubator-pagespeed-ngx/blob/master/src/ngx_event_connection.cc#L157 is necessary. It's been a while, so my memory isn't crystal clear, but I think the that when `NgxEventConnection` runs into the situation where it repeatedly cannot write, a change is needed: - A queue to buffer writes (ordering is important) - A timer, to ensure processing events in the flow when there are no subsequent i/o wakeups The code that now writes to the pipe should first check the queue and process any buffered writes, and then proceed as normal (though possibly disarming the timer if the queue was fully drained ). Similarly the new code associated to the new timer event should also processes buffered up writes. Unfortunately I don't tink I will have time soon to make this happen, but maybe the braindump above will enthuse someone to write a fix, or else it might serve as a note to future me :-) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] zz9pzza commented on issue #1380: nginx worker 100% cpu usage (spinning on write returning EAGAIN)
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 running 1.13.35.2 which I believe includes that patch on kernel 5.9.0-0.bpo.2-amd64 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] urifoox commented on issue #1380: nginx worker 100% cpu usage (spinning on write returning EAGAIN)
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 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] zz9pzza commented on issue #1380: nginx worker 100% cpu usage (spinning on write returning EAGAIN)
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 http://mailman.nginx.org/pipermail/nginx/2021-January/060346.html pagespeed saves us a lot of bandwidth. It seems to me in this case that nothing is being read from the pipe in our situation ? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] Lofesa commented on issue #1720: URL is not in cache
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 the server with pagespeed module. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] uhlhosting commented on issue #1720: URL is not in cache
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 also enabled. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] Lofesa commented on issue #1720: URL is not in cache
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;? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-mod] hycday closed issue #2054: Optimization doesn't happen on images loaded via "Load More"
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 above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-mod] hycday edited a comment on issue #2054: Optimization doesn't happen on images loaded via "Load More"
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 who have the filename changed to something like "image.jpg.pagespeed.ic.qRBF-wROiM.webp"), and in the headers of the loaded images via ajax (in below example it is "image2.jpg"), I can see : `content-type: image/webp etag: W/"PSA-aj-j17OKP5Yp5"` so i guess IPRO is working... thank you and sorry for the false alarm, i could not find any documentation on that, and your answer gave all the right details away. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-mod] hycday edited a comment on issue #2054: Optimization doesn't happen on images loaded via "Load More"
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 log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-mod] hycday commented on issue #2054: Optimization doesn't happen on images loaded via "Load More"
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 the filename changed to something like "image.jpg.pagespeed.ic.qRBF-wROiM.webp"), and in the headers of the loaded images via ajax (in below example it is "image2.jpg", I can see : `content-type: image/webp etag: W/"PSA-aj-j17OKP5Yp5"` so i guess IPRO is working... thank you and sorry for the false alarm, i could find any documentation on that and your answer gave all details away. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-mod] Lofesa commented on issue #2054: Optimization doesn't happen on images loaded via "Load More"
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 the headers, but are optimized in some way, not fully opitmized. How you can test it´s IPRO optimized... by the Etag headers you must see some like Etag: "PSA/x" and maybe the conten-type header is set to image/webp but the file extensions remain as jpg. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-mod] hycday opened a new issue #2054: Optimization doesn't happen on images loaded via "Load More"
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, and they are optimized (I can see the 'pagespeed' in the filenames, as well as the right header). I have a "Load More" button. When I press it, it loads additional images, but the pagespeed doesn't affect them and those images are 'untouched'. Is there a way to fix that ? thanks for your help This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] uhlhosting commented on issue #1720: URL is not in cache
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 /www/server/nginx/conf/nginx.conf:18 2021/01/16 14:02:28 [warn] 445981#445981: pagespeed: cannot set gzip, command not found in /www/server/nginx/conf/nginx.conf:18 2021/01/16 14:03:04 [warn] 445981#445981: pagespeed: cannot set gzip, command not found in /www/server/nginx/conf/nginx.conf:18 2021/01/16 14:03:25 [warn] 445981#445981: pagespeed: cannot set gzip, command not found in /www/server/nginx/conf/nginx.conf:18 Now I havent altered the nginx.conf . This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] vphantom commented on issue #1154: POSITION_AUX=true broken in nginx 1.9.11+
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 go that far _and_ use mod_pagespeed. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] oschaaf commented on issue #1154: POSITION_AUX=true broken in nginx 1.9.11+
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 was to get some feedback on the feature and then flip the switch after building some confidence through that, as the change itself is simple but its implications may not be. See this (6 year old :-) ) [PR review discussion] (https://github.com/apache/incubator-pagespeed-ngx/pull/906#issuecomment-74089777). This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] zamanuhina commented on pull request #1617: Update Nginx in Docker
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. > > https://cloud.docker.com/repository/docker/extremeshok/nginx-pagespeed Hello, backward compatibility? If I just change pagespeed/nginx-pagespeed to extremeshok/nginx-pagespeed should everything work right away? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] vphantom edited a comment on issue #1154: POSITION_AUX=true broken in nginx 1.9.11+
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 when attempting to start. Errors such as: ```text nginx: master process /usr/share/nginx/sbin/nginx -g daemon off;(net_instaweb::NgxBaseFetch::Initialize(ngx_cycle_s*)+0x63) [0x55fc7158c557] nginx: master process /usr/share/nginx/sbin/nginx -g daemon off;(ngx_spawn_process+0x4fe) [0x55fc7150df53] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7f3c17cfe2e1] 2021/01/14 11:29:26 [alert] 7#0: [ngx_pagespeed 1.13.35.2-0] [0114/112926:FATAL:ngx_base_fetch.cc(74)] Check failed: event_connection == NULL. event connection already set ``` …which might explain why #612 is still open despite #906 and #1155. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] vphantom commented on issue #1154: POSITION_AUX=true broken in nginx 1.9.11+
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 attempting to start. Errors such as: ```text nginx: master process /usr/share/nginx/sbin/nginx -g daemon off;(net_instaweb::NgxBaseFetch::Initialize(ngx_cycle_s*)+0x63) [0x55fc7158c557] nginx: master process /usr/share/nginx/sbin/nginx -g daemon off;(ngx_spawn_process+0x4fe) [0x55fc7150df53] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7f3c17cfe2e1] 2021/01/14 11:29:26 [alert] 7#0: [ngx_pagespeed 1.13.35.2-0] [0114/112926:FATAL:ngx_base_fetch.cc(74)] Check failed: event_connection == NULL. event connection already set ``` …which might explain why #612 is still open despite #906. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] uhlhosting commented on issue #1720: URL is not in cache
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. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] 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 suc
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 problem. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] Lofesa commented on issue #1720: URL is not in cache
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 but no store it in their cache. Pagespeed can´t cache html. Pagespeed "remember" this for some time (short time) and tries to optimize again when the url is requested, so fires the message again. Is safe to ignore these messages, and you can´t do anything to suppress, maybe changing the log level to only show errors. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] 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 su
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: [ngx_pagespeed 1.13.35.2-0] http://xxx.xxx.xxx.xxx/ (connecting to:lb1.i):0:Error status=670002 (Name or service not known) serf_connection_create2 The module isn't able to fetch its input resources. It might be good to check https://www.modpagespeed.com/doc/faq#warning-fetch-rate and possibly https://www.modpagespeed.com/doc/https_support This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [incubator-pagespeed-ngx] ashishkpal 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
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 1.13.35.2-0] http://xxx.xxx.xxx.xxx/ (connecting to:lb1.i):0:Error status=670002 (Name or service not known) serf_connection_create2 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
