On Feb 11, 2014, at 1:30 PM, Matt Ingenthron <[email protected]<mailto:[email protected]>> wrote:
I'm not sure if it's relevant here, but while the username:password@ is relatively common and frequently does what you expect, it actually is not part HTTP standards. It's defined in <http://www.ietf.org/rfc/rfc1738.txt> RFC 1738<http://www.ietf.org/rfc/rfc1738.txt>: Uniform Resource Locators, the specification of URL syntax: 3.1. Common Internet Scheme Syntax While the syntax for the rest of the URL may vary depending on the particular scheme selected, URL schemes that involve the direct use of an IP-based protocol to a specified host on the Internet use a common syntax for the scheme-specific data: //<user>:<password>@<host>:<port>/<url-path> Some or all of the parts "<user>:<password>@", ":<password>", ":<port>", and "/<url-path>" may be excluded. The scheme specific data start with a double slash "//" to indicate that it complies with the common Internet scheme syntax. I've seen some things that do not support it. IIRC, it was removed and is recommended against in the HTTP URI scheme. It's true that not all code out there that handles HTTP URLs checks for the username/password portion. But in the CouchDB replication API this is how you specify username/password based authentication, and the same goes for Couchbase Lite. --Jens -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/1CD11985-270F-4035-AAD5-8119E57ADD3E%40couchbase.com. For more options, visit https://groups.google.com/groups/opt_out.
