Bug 15529 - [S60] setRequestHeader in XMLHttpRequest does not work
Summary: [S60] setRequestHeader in XMLHttpRequest does not work
Status: CLOSED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore JavaScript (show other bugs)
Version: 523.x (Safari 3)
Hardware: S60 Hardware S60 3rd edition
: P2 Major
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-16 02:58 PDT by Milos Endrle
Modified: 2011-03-21 11:53 PDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Milos Endrle 2007-10-16 02:58:35 PDT 
We are test javascript code (Ajax) which add custom header to request by setRequestHeader. setRequestHeader does not return any error but header does not send in POST request. In our debug tool (javascript object browser) we see that XMLHttpRequest has two definitions for setRequestHeader and probably this is problem.

We are test this behaviour on Nokia E65 and E61i. Other information from navigator object in tested phones:
productSub: 20030107
userAgent: Mozilla/5.0 (SymbianOS/9.1;U;en-us;) AppleWebKit/413 (KHTML, like Gecko) Safari/413 es65

On other Safari based devices working setReqeustHeader properly (iPhone, Safari for Windows).
Comment 1 Bradley Morrison 2008-04-09 11:31:56 PDT 
Bulk update of s60 bugs - tagging and closing.
Comment 2 Bradley Morrison 2008-04-09 11:39:37 PDT 
Bulk closing of all s60 platform bugs. 

Sorry for the noise!
Comment 3 Joel Parks 2011-03-21 11:53:39 PDT 
re-purposing InTSW keyword for use by QtWebkit team