called images are not getting converted in webp

IMCL NOC

unread,

Apr 15, 2017, 8:19:58 AM4/15/17

to ngx-pagespeed-discuss, Krishna Pandey, Noida

Dear Team,

My images domain is www.example.com

& other html web domani is www.abcd.com

when an image url of www.example.com/krishna.jpg is called in www.abcd.com/open.html

images is not converted in webp

On the other side when it called from same domain both image & html it is working

please help me for this

Thanks

Krishna

Otto van der Schaaf

unread,

Apr 15, 2017, 4:57:32 PM4/15/17

to ngx-pagespeed-discuss, Krishna Pandey, Noida

If you do not control www.example.com, you can let ngx_pagespeed proxy that domain, see

https://modpagespeed.com/doc/domains#MapProxyDomain

If you do control www.example.com and it also has ngx_pagespeed deployed, you need to authorize www.example.com in the server{} block that listens to www.abcd.com. You can do so by adding the following to nginx.conf:

pagespeed Domain www.example.com;

Subsequently, you need to make sure that the same pagespeed configuration applies to www.example.com and www.abcd.com

(Meaning that if www.example.com is served via the same server{} as www.abcd.com, or inherits the pagespeed configuration from the http{} block, you should be all set by just authorizing the domain).

Otto

--
You received this message because you are subscribed to the Google Groups "ngx-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ngx-pagespeed-di...@googlegroups.com.
Visit this group at https://groups.google.com/group/ngx-pagespeed-discuss.
For more options, visit https://groups.google.com/d/optout.

IMCL NOC

unread,

Apr 16, 2017, 2:37:14 AM4/16/17

to ngx-pagesp...@googlegroups.com, Krishna Pandey, Noida

Hi ,

Thanks for the fast reply.

Still its not working

Url for testing

http://www1.bhaskar.com/krishna.html

host entry to be done for testing

220.226.103.203 i9.dainikbhaskar.in

220.226.103.252 www1.bhaskar.com

Krishna

On Sun, Apr 16, 2017 at 2:27 AM, Otto van der Schaaf <osc...@we-amp.com> wrote:

If you do not control www.example.com, you can let ngx_pagespeed proxy that domain, see
https://modpagespeed.com/doc/domains#MapProxyDomain

If you do control www.example.com and it also has ngx_pagespeed deployed, you need to authorize www.example.com in the server{} block that listens to www.abcd.com. You can do so by adding the following to nginx.conf:

pagespeed Domain www.example.com;

Subsequently, you need to make sure that the same pagespeed configuration applies to www.example.com and www.abcd.com
(Meaning that if www.example.com is served via the same server{} as www.abcd.com, or inherits the pagespeed configuration from the http{} block, you should be all set by just authorizing the domain).

Otto

On Sat, Apr 15, 2017 at 2:19 PM IMCL NOC <teami...@gmail.com> wrote:

Dear Team,

My images domain is www.example.com
& other html web domani is www.abcd.com

when an image url of www.example.com/krishna.jpg is called in www.abcd.com/open.html

images is not converted in webp

On the other side when it called from same domain both image & html it is working

please help me for this

Thanks
Krishna

--
You received this message because you are subscribed to the Google Groups "ngx-pagespeed-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to ngx-pagespeed-discuss+unsub...@googlegroups.com.

Visit this group at https://groups.google.com/group/ngx-pagespeed-discuss.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "ngx-pagespeed-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ngx-pagespeed-discuss/GZ0M2BIjZMY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ngx-pagespeed-discuss+unsub...@googlegroups.com.

IMCL NOC

unread,

Apr 16, 2017, 7:34:11 AM4/16/17

to ngx-pagesp...@googlegroups.com, Krishna Pandey, Noida

Hi Otto,

Thanks again.

We added same rules at html web-server as of images server now its working fine at local level.

Now issue is When i open the URL first from chrome, html server is rewriting the files & it gets cached at Akamai-CDN end as .webp URL. Same URL in Mozilla its not opening the image as URL rewritten is "*.webp"

When the html URL is open in Mozilla first then it gives .jpg file for both browsers Mozilla & chrome as again html get cached in Akamai-CDN end.

Please help me with this.

Krishna

To unsubscribe from this group and stop receiving emails from it, send an email to ngx-pagespeed-discuss+unsubscri...@googlegroups.com.

Visit this group at https://groups.google.com/group/ngx-pagespeed-discuss.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "ngx-pagespeed-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ngx-pagespeed-discuss/GZ0M2BIjZMY/unsubscribe.

To unsubscribe from this group and all its topics, send an email to ngx-pagespeed-discuss+unsubscri...@googlegroups.com.

Otto van der Schaaf

unread,

Apr 16, 2017, 11:39:46 AM4/16/17

to ngx-pagesp...@googlegroups.com, Krishna Pandey, Noida

As the optimized html will be different for different user-agents with your configuration, some care must be taken.

Pagespeed serves the HTML as uncacheable, but apparently that is overridden by the CDN configuration. This may not work well.

With your setup, some experimentation may be needed to get the best results.

Maybe OptimizeForBandwidth mode will serve your cause better:

https://modpagespeed.com/doc/optimize-for-bandwidth

This mode would allow you to cache the html at the CDN level.

If you can let the CDN´s cache vary on user-agent, it should be possible to also serve webp in-place:

https://modpagespeed.com/doc/system#in_place_optimize_for_browser

Otto

To unsubscribe from this group and stop receiving emails from it, send an email to ngx-pagespeed-di...@googlegroups.com.

Visit this group at https://groups.google.com/group/ngx-pagespeed-discuss.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "ngx-pagespeed-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ngx-pagespeed-discuss/GZ0M2BIjZMY/unsubscribe.

To unsubscribe from this group and all its topics, send an email to ngx-pagespeed-di...@googlegroups.com.

Visit this group at https://groups.google.com/group/ngx-pagespeed-discuss.
For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to the Google Groups "ngx-pagespeed-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to ngx-pagespeed-di...@googlegroups.com.

Joshua Marantz

unread,

Apr 16, 2017, 2:24:43 PM4/16/17

to ngx-pagesp...@googlegroups.com, Krishna Pandey, Noida

Everything Otto says is right, and I want to add a few things.

For this functional problem to occur, your Akamai setup must be ignoring the Vary headers that mod_pagespeed puts on HTML (Vary:User-Agent) and/or images (Vary:Accept). If you want to cache your mod_pagespeed-optimized HTML at Akamai (or any other CDN) you need to do one of two things:

set up Akamai to respect all Vary headers OR
tell mod_pagespeed to OptimizeForBandwith (Otto gave the link).

If you tell mod_pagespeed to OptimizeForBandwidth, you can let Akamai ignore Vary:User-Agent, but you must tell it to respect Vary:Accept. Otherwise it will cache webp images and serve them to browsers that doe not accept webp.

This should all be configurable in your Akamai setup. I don't know the details of how to configure Akamai though.

For more discussion on this topic, please see https://github.com/pagespeed/mod_pagespeed/issues/817

To unsubscribe from this group and stop receiving emails from it, send an email to ngx-pagespeed-discuss+unsub...@googlegroups.com.

Visit this group at https://groups.google.com/group/ngx-pagespeed-discuss.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "ngx-pagespeed-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ngx-pagespeed-discuss/GZ0M2BIjZMY/unsubscribe.

To unsubscribe from this group and all its topics, send an email to ngx-pagespeed-discuss+unsub...@googlegroups.com.

Visit this group at https://groups.google.com/group/ngx-pagespeed-discuss.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "ngx-pagespeed-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to ngx-pagespeed-discuss+unsub...@googlegroups.com.

Visit this group at https://groups.google.com/group/ngx-pagespeed-discuss.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "ngx-pagespeed-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to ngx-pagespeed-discuss+unsub...@googlegroups.com.

Reply all

Reply to author

Forward