Bug 254158
| Summary: | httpHeaderField always returns string | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Anne van Kesteren <annevk> |
| Component: | WebCore Misc. | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | CC: | cdumez, webkit-bug-importer, youennf |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Anne van Kesteren
This makes it impossible to distinguish between a missing header and a header that is present whose value is the empty string.
It would be better if we were precise about this as Fetch and HTTP are too.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/106944735>
Chris Dumez
String has a null state in WebKit.
This should be distinguishable already. `string.isNull()` -> header is missing. `string.isEmpty() && !string.isNull()` -> header is present but has no value.
Chris Dumez
I suggest we mark this bug as invalid unless I missed something.
Chris Dumez
You could also use `httpHeaderFields().contains()`.
youenn fablet
The bug is more that, apparently, some code paths are using isEmpty() while they should probably use isNull().
Anne van Kesteren
Ah, I didn't realize that! Let's close this as INVALID then. I'll follow-up with more detailed bugs as I come across things.