Bug 151360 - XMLHTTPRequest.status only works with HTTP(S) URLs
Summary: XMLHTTPRequest.status only works with HTTP(S) URLs
Status: RESOLVED WORKSFORME
Alias: None
Product: konqueror
Classification: Applications
Component: khtml (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-26 09:04 UTC by Marcus Better
Modified: 2023-01-12 05:16 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 Marcus Better 2007-10-26 09:04:26 UTC
Version:            (using KDE KDE 3.94.0)
Installed from:    Debian testing/unstable Packages
OS:                Linux

When used with e.g. file:// URLs to load a local file, XMLHTTPRequest.status always returns undefined. I believe this is because it only handles HTTP status responses:

Here is the relevant code in kdelibs/khtml/ecma/xmlhttprequest.cpp:

ValueImp *XMLHttpRequest::getStatus() const
{
  return httpStatus(responseHeaders);
}

But there are no responseHeaders for file:// URLs.
Comment 1 Allan Sandfeld 2010-04-16 19:32:21 UTC
Of course, local files are not fetched using http, and does not have http response codes. 

Have you tested what other browsers does?
Comment 2 Marcus Better 2010-04-21 14:37:40 UTC
(In reply to comment #1)
> Have you tested what other browsers does?

FF and IE return 0 for success, and nonzero otherwise.
Comment 3 Andrew Crouthamel 2018-11-02 22:59:04 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-11-16 05:35:26 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version?

Thank you for helping us make KDE software even better for everyone!
Comment 5 Justin Zobel 2022-12-13 02:53:59 UTC
Thank you for reporting this issue in KDE software. As it was reported on an older version, can we please ask you to see if you cazn reproduce the issue with a more recent software version?  
  
If you can confirm this issue still exists in a recent version, please change the version field and the status to "REPORTED" when replying. Thank you!
Comment 6 Bug Janitor Service 2022-12-28 05:23:20 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Bug Janitor Service 2023-01-12 05:16:20 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!