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

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

Lofesa commented on issue #1674: Varnish with PageSpeed module
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1674#issuecomment-567856397
 
 
   > Thank you, now the domain is authorized, but :6081 Varnish side is requesting some assets over https.
   
   Maybe these assets are bypassing varnish? I will say, request that varnish send to the backend w/o any change on it.
   
   > 
   > UPD: It looks like http://test.onlinemagento.com:6081/?PageSpeedFilters=+debug is working, but on 443 still not found.
   
   So now if you request directly the varnish it work, rigth?
   Then the next step is debug the comunication between ngin ssl to varnish.
   Whats happens if the nginx ssl become non ssl? For testing purposes.
   
   Ummm I tried to fecht this: 
   `https://test.onlinemagento.com/static/frontend/Sm/ogalo/pl_PL/css/A.print.css.pagespeed.cf.gWpod0Sgg1.css`
   
   and seems that is magento that tries to search a file:
   
   ```
   Unable to resolve the source file for 'frontend/Sm/ogalo/pl_PL/css/A.print.css.pagespeed.cf.gWpod0Sgg1.css'
   <pre>#1 Magento\Framework\App\StaticResource->launch() called at [vendor/magento/framework/App/Bootstrap.php:257]
   #2 Magento\Framework\App\Bootstrap->run() called at [pub/static.php:13]
   </pre>
   
   
   ```
   P.D.: I´m new to this stuff, never have tried this config nor used varnish, so I´m blind in this issue and maybe I´m proposing things that don´t make sense. Sorry for that.
   
   
   
   
   
   

----------------------------------------------------------------
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