Bug 30666 - Web Inspector: Error - requestContentType [undefined] is not an object
Summary: Web Inspector: Error - requestContentType [undefined] is not an object
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (Deprecated) (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Joseph Pecoraro
Depends on:
Reported: 2009-10-22 00:46 PDT by Joseph Pecoraro
Modified: 2009-10-22 18:26 PDT (History)
7 users (show)

See Also:

[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+
Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Joseph Pecoraro 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.
Comment 1 Joseph Pecoraro 2009-10-22 00:48:14 PDT
Created attachment 41644 [details]
[PATCH] Check for undefined first

Handle a case where this could be undefined.
Comment 2 Pavel Feldman 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
Comment 3 Joseph Pecoraro 2009-10-22 08:24:08 PDT
Landed in http://trac.webkit.org/changeset/49938
r49938 = 0b42938e711aa8e033aa62dcdb2dd6691106cdfa
Comment 4 Patrick Mueller 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.