Ask Different is a question and answer site for power users of Apple hardware and software. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I know it is possible to save form username/passwords on the iPad's Safari browser. The thing I can't do is to save .htaccess username and passwords. In case you don't know what those are, it's when a webpage is protected and you can't even see the page without authenticating. It usually displays a popup window so you can authenticate.

Is it possible to save this type of credentials?

share|improve this question
up vote 1 down vote accepted

For a more secure solution, I'd suggest 1Password for iPad. It has many useful features, not the least of which are auto-generation of strong passwords (so you can use a different password on each site) and strong encryption of your passwords. You can use 1Password with HTTP Authentication.

share|improve this answer

This is HTTP Authentication and the iPad cannot "remember" the credentials of these sorts of logins. It has no problems with a normal web form however.

If you are happy to have your username and password stored in plain text on a bookmark in Safari however, there is a way to allow you to login without filling out those details again.

Just visit the site with the following formatted url :

Rememer to change the 3 obvious variables (username, password and domain). This should log you straight in. You can save this as a book mark and then use that going forward.

The username and password must be URL encoded if they contain any special characters.

Just remember that anyone who picks up your iPad could view the bookmarks and see the clear text username and password, so I wouldn't use this on your banks website :)

Hope this helps.

share|improve this answer
If you bank uses basic/digest authentication, stop using it... Chiefly because you don't know if they're using basic or digest authentication. – Jason Salaz May 6 '11 at 21:43
Also note that using this method would mean you are sending your username and password in plaintext so anyone on your network could potentially see this. If you're not connected to your home wifi, then this is not a good idea. – styfle May 6 '11 at 23:21
@JasonSalaz I can't imagine for the life of me why that matters. Most banks use "forms" authentication and that certainly isn't any more inherently secure than http basic authentication, presuming the connection is made over HTTPS. On the other hand, there seem to be people who think a site is secure if it's using digest authentication but not using HTTPS, which is a fallacy. Apple preventing the iOS Safari browser from saving basic passwords is irritating. – Craig Jul 16 at 4:25
I think I agree with you, I argue that HTTP authentication is terrible for UX (though browser's have gotten smart about toning how modal the prompts are), but security-wise you're right. HTTPS > Basic or Digest by far. – Jason Salaz Jul 16 at 4:55
Also, that 5 year bump, though... – Jason Salaz Jul 16 at 4:55

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.