password protected directory problem

[dennisvwu]

I was able to add 2 out of my 3 wordpress blogs using my 1st gen iPhone.

the only difference between the first two sites and the third site is that i password protected the web-blog directory so that the user would have to provide a login/password before they can see the page.

when i turn the directory password protection off, i am able to add the site sucessfully and everything works fine on the iphone but when i turn the directory password, the wordpress app gives me the "Communication Error - Operation could not be completed. (NSURLErrorDomain error - 1012)

if i remove the blog from the wordpress app and try to add it back in while the directory password protection is on, i get the "XML-RPC" not found error.

[dennisvwu]

www.dennisvwu.com/DesiNme <-- i am trying to add that site

[josephscott]

Right, the additional web server level password requirement prevents the iPhone app from communicating with your blog.

[josephscott]

This is something that we could potentially support, the app could watch for an authorization required response and ask for the username and password to use. It would then have to include the authorization header in each XML-RPC request.

Currently we have a number of bug reports and new features going in, so I'm going to bump this out to 1.2.

[dennisvwu]

awesome!

Thanks Joesphscott. Keep up the good work!

[bael]

This would be great !!!

Thanks.

[ckelley]

I am anxiously awaiting this fix. If I can help in any way, please contact me! Thanks!

[dorkus]

I, too, am anxiously awaiting this fix. I currently can't use this app, due to having .htaccess enabled on my site.

When I first setup the blog on the app, and enter my username and password via the url (ex: ​http://username:password@www.blog.com) it actually works. I can create a post, and utilize the regular functionality of the app.

The problem: anytime after the initial setup period, and after I post once, I'll receive that "Communication Error - Operation could not be completed. (NSURLErrorDomain error - 1012)" error, and it will no longer work. I'm not sure where the problem lies. Is it within the HTML spec to not allow, or reject, a url with a username and password when the site isn't requesting authentication against it? I ask this, because I think the username/password may be cached in the browser, yet since I have entered this info in the url, it may not want it for EACH time the url is accessed.

Regardless, even though it works after the first time, it won't work at anytime thereafter.

I would greatly appreciate any kind of fix for this. As of right now, I can't take advantage of this app.

Thanks for your time.

[ckelley]

dorkus - Thanks for the workaround! It works like a charm! All you have to do for subsequent entries, is to re-enter the Wordpress password! It works time and time again! I'd still like to see this fixed eventually, but in the meantime I love having a workaround! Thanks again!

[dorkus]

The recent update to 1.2 actually broke passing the username/password through the URL. After you setup the blog, it'll go back to the main wordpress screen, but you can never load the blog after that. The circle busy indicator stays in an infinite loop.

ckelley: Are you able to pass the info through the URL? Glad it worked for a short while.

This update looks great, landscape and better photo handling. But, unfortunately, I still can't use it.

Any help would be appreciated. Thanks!

[ckelley]

Replying to dorkus:

The recent update to 1.2 actually broke passing the username/password through the URL. After you setup the blog, it'll go back to the main wordpress screen, but you can never load the blog after that. The circle busy indicator stays in an infinite loop.

ckelley: Are you able to pass the info through the URL? Glad it worked for a short while.

This update looks great, landscape and better photo handling. But, unfortunately, I still can't use it.

Any help would be appreciated. Thanks!

Dorkus -

I'm experiencing the same issues with the new version! :( I only recently updated, so I haven't checked the status of this bug in quite some time since the work-around worked!

Is there a way to go to the previous version of the app? Next time I should check for reported issues before I upgrade!!!!!

[raanan]

@josephscott -- is this something being actively worked on ?

[iammattthomas]

Fixed by r674.