| 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 | ||
|
Description
Anne van Kesteren
2023-03-20 08:31:56 PDT
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. I suggest we mark this bug as invalid unless I missed something. You could also use `httpHeaderFields().contains()`. The bug is more that, apparently, some code paths are using isEmpty() while they should probably use isNull(). 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. |