Search the Community
Showing results for tags 'https'.
At the present time there does not seem to be a reasonable method to retrieve In-World Textures from a Secure HTTPS web page. For example, if you try using the URL: https://secondlife.com/app/image/d2773340-b1dd-b030-e9bf-2c2851000283/2 That resolves to the following URL: http://texture-service.agni.lindenlab.com/d2773340-b1dd-b030-e9bf-2c2851000283/320x240.jpg/ But notice that the first part has been changed from https:// to http:// ... GACK! Any secure web page that attempts to include an In-World Texture will trigger a "mixed content" warning in every browser out there. If you try and pre-resolve the second URL but manually stick an https:// on the front, you get an interesting error. (In Chrome it's a Privacy Error because the source is not secure.) Sooooo .. Linden Lab? What are your plans for providing a secure web service for In-World Textures? Can we get something going since it seems Secure Hosting is a nearly free and easily obtained technology these days? In the meantime, does anyone have any hacks or tricks that might get around this issue ... or maybe just sees that I've totally missed some obvious thing. I'd appreciate any help that folks can provide. Thanks in advance.