> On 05 Feb 2015, at 22:05, Esteban A. Maringolo <emaring...@gmail.com> wrote: > > 2015-02-05 16:18 GMT-03:00 Max Leske <maxle...@gmail.com>: >> Addendum: I suspect that this practice will prevent CORS problems. If a page >> uses https to get the script for instance and the script calls another url >> on the same server but with http only, the request will fail (that’s a known >> problem with some of the Facebook scripts). > > Exactly. > > Plus the references are also independent of the requested transport > protocol (HTTP or HTTPS), so if the request starts on HTTP and no > automatic redirection to HTTPS is applied, all links continue to work, > as well as if the first request happens with HTTPS. > > Regards!
Yes, makes sense. Now in Zn #bleedingEdge === Name: Zinc-Resource-Meta-Core-SvenVanCaekenberghe.46 Author: SvenVanCaekenberghe Time: 5 February 2015, 10:32:09.544628 pm UUID: 7364336d-5e0f-485b-9c2e-242c33d7a24d Ancestors: Zinc-Resource-Meta-Core-SvenVanCaekenberghe.45 Extend ZnUrl>>#withRelativeReference: to handle network relative references (thanks Peter Kenny & Max Leske for convincing me that this is needed) === Name: Zinc-Resource-Meta-Tests-SvenVanCaekenberghe.32 Author: SvenVanCaekenberghe Time: 5 February 2015, 10:32:28.130956 pm UUID: 28846eea-cd9a-4a27-b54f-d9a1ac171fbd Ancestors: Zinc-Resource-Meta-Tests-SvenVanCaekenberghe.31 Extend ZnUrl>>#withRelativeReference: to handle network relative references (thanks Peter Kenny & Max Leske for convincing me that this is needed) === Sven
