[GitHub] [incubator-pagespeed-ngx] Lofesa edited a comment on issue #1674: Varnish with PageSpeed module

[GitBox <gi...@apache.org>]

Lofesa edited a comment on issue #1674: Varnish with PageSpeed module
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1674#issuecomment-567905708
 
 
   But when you hit varnish the asset is here, so varnish cached it.... and when you hit nginx 8080 it manages to resolve the .pagespeed. thing, no magento is involved to return the asset.
   Recap on this:
   1.- The client send a https request to nginx SSL
   2.- The nginx SSL do a http request to varnish (is a redirect or a proxy_pass?)
   3.- The varnish do a http request to the nginx 8080.
   You have tried:
   1.- Hiting nginx 8080 and it work w/o issues
   2.- Hiting varnish and it works w/o issue ( is rigth?)
   3.- Hiting nginx SSL don´t work.
   
   So the questions I see here: 
   1.- Is the nginx SSL doing a http request to varnish?  Seems that yes cause if not the non rewriten resources returns a 404 too.
   2.- So why the .pagespeed. get the 404? Maybe these resources have https when go to varnish and/or varnish send it untouched to nginx 8080? 
   3.- Why magento try to find a file with .pagespeed. ? This request sould be catched by pagespeed module and do the stuff to search it in the pagespeed cache.
   
   Have you tried my last sugestion?
   >Whats happens if the nginx ssl become non ssl? For testing purposes.
   
   Make the nginx SSL respond to the http 80 w/o redirect to the 443 and sending the request to varnish and see whats happens.
   
   EDIT: Take a look at `varnishlog` this command uotput the varnish log. Is a command you must run as roor ( sudo) and it output what varnish is doing. With -w <file name> it stores the log in a file.
   

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services