Try generating the basic with header yourself On Nov 13, 2013 6:43 PM, "Hank Knight" <[email protected]> wrote:
> I tried encoding the @ but that does not work either! > > curl -kX -u nlbdmobz%40sharklasers.com:password123 POST \ > https://zqzqzqz555.couchappy.com/urls \ > -d "{}" -H "Content-Type: application/json" > > Please test it with the real database and login information I provided. > > Unfortunately I have to use curl here and I need to figure out what to > do about "@". > > Thanks for the help! > > > On Wed, Nov 13, 2013 at 10:36 PM, Stanley Iriele <[email protected]> > wrote: > > Yeah that's a funny case...I usually avoid doing that for that specific > > reason... Why not base64 encode it and send the file in a formatted > header > > yourself instead of relying on curl?... > > On Nov 13, 2013 6:32 PM, "Hank Knight" <[email protected]> wrote: > > > >> The username is > >> [email protected] > >> > >> And the password is > >> password123 > >> > >> Please test it: > >> https://zqzqzqz555.couchappy.com/ > >> > >> Putting the password in the middle of the username does NOT work. > >> > >> The real question relates to escaping the @. > >> > >> Believe me, I have spent quite a bit of time Googling this and found > >> nothing. > >> > >> > >> > >> > >> > >> On Wed, Nov 13, 2013 at 10:15 PM, Jens Alfke <[email protected]> > wrote: > >> > > >> > On Nov 13, 2013, at 6:03 PM, Hank Knight <[email protected]> > wrote: > >> > > >> >> What is wrong with this? > >> >> > >> >> curl -kX -u [email protected]:password123 POST \ > >> >> https://zqzqzqz555.couchappy.com/urls \ > >> >> -d "{}" -H "Content-Type: application/json" > >> >> > >> >> I get an error: > >> >> curl: (6) Couldn't resolve host 'sharklasers.com:password123' > >> > > >> > Wrong syntax. It should be nlbdmobz:[email protected] . > >> > > >> > The syntax is weird, but it’s really not hard to find out how it > works. > >> Try googling for [url password syntax] and the top few hits all look > like > >> good info. > >> > > >> > —Jens > >> >
