Reply to thread

Message

<blockquote data-quote="Macemore" data-source="post: 466976" data-attributes="member: 6113">You're probably not getting redirected to www.yourwebsite.com on IOS judging by your certificate CN=<a href="http://www.beehost.rs" target="_blank">www.beehost.rs</a> , ask for another certificate and seperate via commans your &quot;multiple&quot; domains (this being beehost.rs and www.beehost.rs).The reason this happens is because www. was to tell the system to connect to the world wide web, back when the internet was actually intranet. This old bullshit has continued to today and thus you must assume clients may connect by <a href="http://www.beehost.rs" target="_blank">www.beehost.rs</a> AND beehost.rs, fortunately for most browsers they usually default to that, unless the subdomain doesn't exist in the DNS records. This also varies between browsers and browser versions.[automerge]1611210177[/automerge]Upon further analysis it appears your content management system is actually trying to account for this by forwarding us manually to the www. subdomain (see GIF), so whatever plugin is doing that or if its just built in I'd raise a bug flag with the creator of either. Clearly not working on your client, also its still best practice to SSL www. of all domains planning on accepting browser based traffic. This would fix the issue regardless of the bug in your code, too.[URL unfurl=&quot;true&quot;]https://i.imgur.com/vWBsLvb.mp4[/URL]</blockquote>

[QUOTE="Macemore, post: 466976, member: 6113"] You're probably not getting redirected to [B]www[/B].yourwebsite.com on IOS judging by your certificate CN=[URL="http://www.beehost.rs"]www.beehost.rs[/URL] , ask for another certificate and seperate via commans your "multiple" domains (this being beehost.rs and [B]www[/B].beehost.rs). The reason this happens is because www. was to tell the system to connect to the world wide web, back when the internet was actually intranet. This old bullshit has continued to today and thus you must assume clients may connect by [URL="http://www.beehost.rs"]www.beehost.rs[/URL] AND beehost.rs, fortunately for most browsers they usually default to that, unless the subdomain doesn't exist in the DNS records. This also varies between browsers and browser versions. [automerge]1611210177[/automerge] Upon further analysis it appears your content management system is actually trying to account for this by forwarding us manually to the www. subdomain (see GIF), so whatever plugin is doing that or if its just built in I'd raise a bug flag with the creator of either. Clearly not working on your client, also its still best practice to SSL www. of all domains planning on accepting browser based traffic. This would fix the issue regardless of the bug in your code, too. [URL unfurl="true"]https://i.imgur.com/vWBsLvb.mp4[/URL] [/QUOTE]

Verification

Reply to thread

Connect with us

Newest members