Bug 136617 - XHR don't remember htaccess authentication data
Summary: XHR don't remember htaccess authentication data
Status: RESOLVED NOT A BUG
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-01 11:26 UTC by elias
Modified: 2011-06-25 06:44 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description elias 2006-11-01 11:26:37 UTC
Version:           3.5.2 (using KDE 3.5.2, Kubuntu Package 4:3.5.2-0ubuntu18.1 dapper)
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.15-27-386

login into a htaccess protected page and start XHR requests in authenticated state, the XHR object doesn't use the authentication data from the login, the data is requested again via popup (user defaults to null here). the XHR request targets the same domain/directory.

i'm not sure if this is a bug, but FF 1.5.0.7 can handle this transparantly.
Comment 1 Marc Boeker 2007-01-28 22:56:55 UTC
Same problem here.
XMLHttpRequest is not able to reuse the provided login data. An auth dialog pops up with the word "undefined" as the username. It seems that the username field is read-only. Perhabst the auth-system conflicts with the kwallet?

I'm using a freh KDE 3.5.6.

Thanks in advance,

Marc Boeker
Comment 2 Marc Boeker 2007-01-28 23:32:56 UTC
I figured out, that this problem exists only while using the prototype javascript framework. a direct xmlhttprequest without using prototype works great. perhabst there is something wrong with the headers, prototype sends to the server?
Comment 3 Marc Boeker 2007-01-28 23:55:41 UTC
Ha! problem fixed :) this bug is also present in safari and it is definitivly prototype specific.

using this patch [1] fixed the problem. as it is not konqueror/khtml related, i think this bug-report can be closed?

[1] http://dev.rubyonrails.org/attachment/ticket/6638/conditionally_pass_username_and_password_patch.diff