search

crowell / modpagespeed_tmp

Automatically exported from code.google.com/p/modpagespeed
Apache License 2.0
0 stars 0 forks source link

Documentation on schema-less URI (e.g. "//example.org") #734

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
I'm having difficulty in working out how to make URIs attach in the form "//" 
as opposed to with "http://" or "https://". Is there a way to do this? It 
doesn't strike me as clear, if it can.

Original issue reported on code.google.com by shri...@gmail.com on 27 Jun 2013 at 8:29

GoogleCodeExporter commented 9 years ago 
I don't understand your question. How does this relate to mod_pagespeed? I 
agree that "//example.org" is a schema-less URL. Are you using schema-less URLs 
on your site? Do you want mod_pagespeed to use them? Please explain more 
clearly.

Original comment by sligocki@google.com on 27 Jun 2013 at 7:23

GoogleCodeExporter commented 9 years ago 
When I use MapRewriteDomain or combine_css, the URLs are prefixed with the full 
schema. I would prefer it not to be.

Original comment by bar...@shrikeh.net on 28 Jun 2013 at 7:14

GoogleCodeExporter commented 9 years ago 
No we don't offer this feature. Why do you want this? Do you terminate your 
HTTPS connection in front of mod_pagespeed and thus want the URLs to work in 
both HTTP and HTTPS?

Original comment by sligocki@google.com on 28 Jun 2013 at 3:27

GoogleCodeExporter commented 9 years ago 
Two reasons really. Firstly, to directly answer your question: yes, we do.

Secondly however, these days, if a site doesn't have availability on both, most 
devops will put in rules to switch anyway (i.e. a redirect or whatever it might 
be). So, if a site is only available on http, it makes no difference if the 
URI's are "http://" or "//" - you'll only be able to access the site through 
the correct protocol anyway. 

It makes more difference if your site uses multiple domains and the domains 
differ in what protocol they offer, but I'd like the option, as it's a byte on 
the wire saving.

If a site only supports one protocol for both the main domain and the shard, it 
might be good to just have // as the default.

Original comment by shri...@gmail.com on 28 Jun 2013 at 3:38

GoogleCodeExporter commented 9 years ago

Original comment by sligocki@google.com on 1 Jul 2013 at 2:09