You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@pagespeed.apache.org by GitBox <gi...@apache.org> on 2019/03/17 20:22:20 UTC

[GitHub] [incubator-pagespeed-ngx] runar opened a new issue #1633: Uncacheable content, but headers seems fine

runar opened a new issue #1633: Uncacheable content, but headers seems fine
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1633

My site is served by nginx on ```www.example.com``` while assets (images, javascript, css) are hosted on ```cdn.example.com```. The latter is a nginx proxy cache, on the same server, fetching the requested files from Amazon S3. This seems to work fine with (almost) all requested files fetched successfully and stored in the local cache.

I’m having some problems getting PageSpeed to process/rewrite all of my files. My favicon, for instance. With the following headers one would believe the file would be processed:

```
HTTP/2 200
server: nginx
date: Sun, 17 Mar 2019 19:56:28 GMT
content-type: image/x-icon
content-length: 11134
last-modified: Tue, 12 Mar 2019 19:55:56 GMT
etag: "0d58e59ee19e0603609cd953c58fcaa0"
cache-control: public, max-age=31536000
x-cache-status: HIT
accept-ranges: bytes
```

However, it is not, and in debug mode the source looks like this:

```
<link rel='shortcut icon' href='//cdn.example.com/favicon.ico.9a68e8979ef3971836e985e05fa766a7.ico' type="image/x-icon">

```

This is just one example, as I’m seeing several files, including images, not processed by PageSpeed.

My site and all assets are served on HTTPS, with 301 redirects from HTTP. Also, the software I use (Invision Community) forces relative URLs when HTTPS is enabled. Is this a potential problem? I’ve set up my domains in the PageSpeed configuration like this:

```
pagespeed Domain http*://cdn.example.com;
pagespeed Domain http*://www.example.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:
users@infra.apache.org

With regards,
Apache Git Services