Bug 310250
| Summary: | Web Inspector: Site Isolation: Network domain sync XHR content fallback | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Blaze Burg <bburg> |
| Component: | Web Inspector | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | inspector-bugzilla-changes, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | 308890 | ||
| Bug Blocks: | |||
Blaze Burg
FrameNetworkAgentProxy::didReceiveData does not have a fallback for synchronous XHR responses that exceed buffer limits or get evicted. In the legacy path, InspectorNetworkAgent checks m_loadingXHRSynchronously and falls back to base64-encoding the raw data via setResourceContent. The SI path cannot replicate this because willLoadXHRSynchronously/didLoadXHRSynchronously are not in the NetworkAgentInstrumentation interface (marked FIXME in LegacyNetworkAgent.h). Without this, sync XHR content may be missing from getResponseBody under Site Isolation.
Fixing this requires adding the sync XHR hooks to NetworkAgentInstrumentation, implementing them in both LegacyNetworkAgent and FrameNetworkAgentProxy, and tracking the sync state in the proxy.
Sub-bug of rdar://143782685.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/172894150>