CUTCODEDOWN
Minimalist Semantic Markup

Welcome Guest
Please Login or Register

If you have registered but not recieved your activation e-mail in a reasonable amount of time, please use our Contact Form for assistance. Include both your username and the e-mail you tried to register with.

Author Topic: Apple mobile stupidity MAYBE fixed?  (Read 239 times)

Jason Knight

  • Administrator
  • Sr. Member
  • *****
  • Posts: 333
  • Karma: +36/-1
    • View Profile
    • CutCodeDown -- Minimalist Semantic Markup
Apple mobile stupidity MAYBE fixed?
« on: 9 Dec 2019, 03:42:39 pm »
For some reason Apple -- and ONLY Apple products -- have been choking on the 301 redirects to force http to https, which is annoying since if you just type in the domain name they assume it's http and don't even try the alternative.

Made worse by the fact their error message says it might have permanently moved -- what the 301 is trying to flipping tell it.

They seem to send a mangled request of some sort I'm still trying to sort out the how/why of -- it's like mangled HTTP 2 headers under a 1.1 declaration -- but for now I THINK I may have thrown enough changes at how they work for them to stop being so stupid about it.

It works in the emulation under xCode, can anyone with a real device that was having problems confirm?
"It is amazing what can be accomplished when nobody cares who gets the credit." -- Kelly Johnson

John_Betong

  • Jr. Member
  • **
  • Posts: 50
  • Karma: +1/-1
    • View Profile
    • The Fastest Joke Site On The Web
Re: Apple mobile stupidity MAYBE fixed?
« Reply #1 on: 10 Dec 2019, 12:54:04 am »
Fantastic because my iPad Mini 2 has been timing out ever since the forum started and now seems OK.
I bet you are pleased to have solved the conflict which was happening on all browsers and not only Sfarari.

I  hope the timeouts do not re-occur.
Retired in the City of Angels where the weather suits my clothes

mmerlinn

  • Junior Member
  • *
  • Posts: 29
  • Karma: +1/-0
  • Nutcake
    • View Profile
Re: Apple mobile stupidity MAYBE fixed?
« Reply #2 on: 10 Dec 2019, 02:47:55 am »
Your site has been working fine for me no matter whether I am using FF 3.6.28 on this Apple or FF 69.0 on the Apple beside me. Never been problems with redirects nor time outs for your site. All of my Apples are desktop so cannot check mobile.
« Last Edit: 10 Dec 2019, 02:49:56 am by mmerlinn »
The soul purr pus of a spell cheque cur is two valley date hour ignore ants.

Jason Knight

  • Administrator
  • Sr. Member
  • *****
  • Posts: 333
  • Karma: +36/-1
    • View Profile
    • CutCodeDown -- Minimalist Semantic Markup
Re: Apple mobile stupidity MAYBE fixed?
« Reply #3 on: 10 Dec 2019, 02:41:23 pm »
Laugh is I think the culprit was ISPConfigs http to https redirection, and not mine. Mine works in the .htaccess works just bloody fine. I've seen this on some client's CPanel installs too so do where the panels put it somehow end up incompatible with iOS?

Very strange indeed. Particularly when it's just iOS that seems to struggle with it.
"It is amazing what can be accomplished when nobody cares who gets the credit." -- Kelly Johnson

John_Betong

  • Jr. Member
  • **
  • Posts: 50
  • Karma: +1/-1
    • View Profile
    • The Fastest Joke Site On The Web
Re: Apple mobile stupidity MAYBE fixed?
« Reply #4 on: 10 Dec 2019, 07:49:28 pm »
The fixes didn't last long, timing out again :(


This is just one of the links which times out and notice the Https prefix.


https://forums.cutcodedown.com/index.php?action=unread


iPad Mini Chrome, version: 78.0.3904.84 is the browser giving the trouble and that browser works fine for four other forums?

Retired in the City of Angels where the weather suits my clothes

Jason Knight

  • Administrator
  • Sr. Member
  • *****
  • Posts: 333
  • Karma: +36/-1
    • View Profile
    • CutCodeDown -- Minimalist Semantic Markup
Re: Apple mobile stupidity MAYBE fixed?
« Reply #5 on: 11 Dec 2019, 12:51:50 am »
iPad Mini Chrome
Since when did crApple start letting third party browsers on the platform? Didn't they used to block that?

Since it seems to be entirely based on the crApple platform I can't find any reason for it. The closest I get to their piles of junk is the xCode emulation, and they seem to work just fine.

Being mobile I don't suppose you could pull me a screencap of a waterfall when it does work? The headers sent on failure? Are you on a local wifi or are you using up your data plan?

There is no reason I can think of now that the "Apple's too stupid to redirect properly" (something that should only be an issue once) is fixed for such problems to occur unless it's on your end.

Side note, I still say "iPad" sounded like they were going into the feminine hygiene business.
« Last Edit: 11 Dec 2019, 12:58:53 am by Jason Knight »
"It is amazing what can be accomplished when nobody cares who gets the credit." -- Kelly Johnson

 

Advertisement