Bug 30666

Summary: Web Inspector: Error - requestContentType [undefined] is not an object
Product: WebKit Reporter: Joseph Pecoraro <joepeck>
Component: Web Inspector (Deprecated)Assignee: Joseph Pecoraro <joepeck>
Status: RESOLVED FIXED    
Severity: Normal CC: aroben, bweinstein, joepeck, pfeldman, pmuellr, rik, timothy
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
Attachments:
Description Flags
[IMAGE] Error Occurring
none
[PATCH] Check for undefined first pfeldman: review+

Joseph Pecoraro
Reported 2009-10-22 00:46:04 PDT
Created attachment 41643 [details] [IMAGE] Error Occurring I do not remember how I produced this error, only that it happened and I took a screenshot of it. Patrick would you agree that such a situation can happen? Apparently inside _refreshFormData a Resource does not have the Content-Type header. Its possible that the resource was pulled from the Cache? Sorry I don't have more info, and I couldn't find out how I produced this. It looks like _refreshFormData is called when in _toggleURLdecoding and _refreshRequestHeaders.
Attachments
[IMAGE] Error Occurring (202.07 KB, image/png)
2009-10-22 00:46 PDT, Joseph Pecoraro 		no flags
Details
[PATCH] Check for undefined first (1.25 KB, patch)
2009-10-22 00:48 PDT, Joseph Pecoraro 		pfeldman: review+
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Joseph Pecoraro
Comment 1 2009-10-22 00:48:14 PDT
Created attachment 41644 [details] [PATCH] Check for undefined first Handle a case where this could be undefined.
Pavel Feldman
Comment 2 2009-10-22 07:38:47 PDT
Comment on attachment 41644 [details] [PATCH] Check for undefined first It'd be nice to know why this is happening. Update the reviewed by field! :P
Joseph Pecoraro
Comment 3 2009-10-22 08:24:08 PDT
Landed in http://trac.webkit.org/changeset/49938 r49938 = 0b42938e711aa8e033aa62dcdb2dd6691106cdfa
Patrick Mueller
Comment 4 2009-10-22 18:26:45 PDT
Better late than never ... (re these comments). Joe, it can certainly occur if there's no Content-Type header, which is perfectly valid. Fix looks fine.
Note You need to log in before you can comment on or make changes to this bug.