- My Forums
- Tiger Rant
- LSU Recruiting
- SEC Rant
- Saints Talk
- Pelicans Talk
- More Sports Board
- Coaching Changes
- Fantasy Sports
- Golf Board
- Soccer Board
- O-T Lounge
- Tech Board
- Home/Garden Board
- Outdoor Board
- Health/Fitness Board
- Movie/TV Board
- Book Board
- Music Board
- Political Talk
- Money Talk
- Fark Board
- Gaming Board
- Travel Board
- Food/Drink Board
- Ticket Exchange
- TD Help Board
Customize My Forums- View All Forums
- Show Left Links
- Topic Sort Options
- Trending Topics
- Recent Topics
- Active Topics
Started By
Message
Can iOS seriously not handle basic http authentication?
Posted on 3/29/25 at 1:19 am
Posted on 3/29/25 at 1:19 am
I set up a simple home network using nginx reverse proxy and letsencrypt SSL to access home assistant and frigate among other services. It wasn’t a big deal at first, but the repeated Auth requests are about to drive me to android.
Any time I access services from ios(tried multiple browsers) I keep getting asked for authentication . Not too annoying because I can just cancel them all as the initial link provided the initial auth, but iOS browsers keep asking for auth over and over and over again. Today, it was like every two seconds. I do not have the same problem with browsers in android, windows, or Linux.
Obviously there is probably another reverse proxy that doesn’t have these issues, and maybe they can pull free ssl certs, but is Apple this stupid in general? This is literally the basic http auth from the #1 web hosting software andiOS hates it.
Settings are simple: allow 0.0.0.0/0 stasify all.
ETA: the “workaround” is using keychains icloud share auth from macOS, so apparently it’s cool if you own a Mac also.
Any time I access services from ios(tried multiple browsers) I keep getting asked for authentication . Not too annoying because I can just cancel them all as the initial link provided the initial auth, but iOS browsers keep asking for auth over and over and over again. Today, it was like every two seconds. I do not have the same problem with browsers in android, windows, or Linux.
Obviously there is probably another reverse proxy that doesn’t have these issues, and maybe they can pull free ssl certs, but is Apple this stupid in general? This is literally the basic http auth from the #1 web hosting software andiOS hates it.
Settings are simple: allow 0.0.0.0/0 stasify all.
ETA: the “workaround” is using keychains icloud share auth from macOS, so apparently it’s cool if you own a Mac also.
This post was edited on 3/29/25 at 1:38 am
Posted on 3/29/25 at 9:01 am to Dallaswho
Radarr is basic auth, never had a problem.
Posted on 3/29/25 at 10:48 am to Dallaswho
Yea it was a PITA getting my wife's iPhone HA app setup with reverse proxy. Had to add it while on locally for it to authenticate, but now works just fine off the local net
Posted on 3/29/25 at 8:45 pm to bluebarracuda
I gave up. I might add SSL between the proxy and my services now to make up for lost security or might not because it’s just a low value home network anyway. I can’t believe I’m still using Apple products. This is probably their last strike. I already lost a decade of message attachments(and cloud backups) due to database corruption. Got zero recovery effort on their end. Enough is enough.
Posted on 3/29/25 at 9:16 pm to j1897
quote:
Radarr is basic auth, never had a problem.
Radarr probably isn’t tossing around random 401s like I suspect frigate is. Still, every browser handles this just fine except ones on iOS.
Posted on 3/31/25 at 8:27 am to Dallaswho
quote:
handles this just fine except ones on iOS
I'm guessing because of the forced usage of Webkit?
Posted on 3/31/25 at 10:01 am to LemmyLives
quote:
I'm guessing because of the forced usage of Webkit?
Don’t know. Not a html guy. That’s prob why all common iOS browsers work the same way. I was just trying to move auth to the front end in a simple way and it was unbearable because the credentials could not be cached. I got them into keychain but that didn’t help either. I guess the service was throwing flags and while all other browsers handled them fine, iOS browsers would freak out and ask for credentials every two seconds even though it didn’t need them. I’m not even messing with it anymore. It’s way easier for me to isolate the back end.
Popular
Back to top
2







