Lofesa commented on issue #1738:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1738#issuecomment-893663481
Hi @SergeyKhlopov
Maybe the issue is in the` return 301 https://domain.com$uri;`
$uri can be "transformed" by nginx, the url can be encoded (f.e. white
spaces
Lofesa commented on issue #1738:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1738#issuecomment-892568661
--
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.
Lofesa commented on issue #1738:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1738#issuecomment-893283879
```
location ~ \.(sh|hta|htp|sql|git|env) {
deny all;
}
```
Lofesa commented on issue #1738:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1738#issuecomment-892903327
Hi @SergeyKhlopov
At a first glance you need to enable pagespeed https fecht:
```
pagespeed FetchHttps enable;
pagespeed SslCertDirectory directory;
Lofesa commented on issue #1738:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1738#issuecomment-892568661
Not even with anonimized data? for the config files I'll say.
Well... you can try thi https://yourdomain.com/?PageSpeedFilters=+debug
And then take a look to the
Lofesa commented on issue #1738:
URL:
https://github.com/apache/incubator-pagespeed-ngx/issues/1738#issuecomment-891662323
Hi
A 403 error sounds more a config error other than a pagespeed issue. If the
response was a 404 is more likely a pagespeed issue, most of the cases a ssl
