Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: 8b4d423492d0e3c74924fe2f8096091d46b77d12
https://github.com/WebKit/WebKit/commit/8b4d423492d0e3c74924fe2f8096091d46b77d12
Author: Matthew Finkel <[email protected]>
Date: 2025-10-28 (Tue, 28 Oct 2025)
Changed paths:
M Source/WebCore/loader/DocumentLoader.cpp
M Source/WebCore/loader/ResourceLoader.cpp
M Source/WebCore/loader/ResourceLoader.h
M Source/WebCore/loader/SubframeLoader.cpp
M Source/WebCore/loader/SubresourceLoader.cpp
M Source/WebCore/loader/cache/CachedResourceLoader.cpp
M Tools/TestWebKitAPI/Tests/WebKitCocoa/Navigation.mm
Log Message:
-----------
Allow resource requests to port 0 when using a custom scheme
https://bugs.webkit.org/show_bug.cgi?id=301532
rdar://157842307
Reviewed by Alex Christensen.
This issue began in some apps with 298983@main where we block connections to
port 0. This change makes an exception that allows using port 0 when using a
scheme that has a custom scheme handler.
* Source/WebCore/loader/DocumentLoader.cpp:
(WebCore::DocumentLoader::willSendRequest):
* Source/WebCore/loader/ResourceLoader.cpp:
(WebCore::ResourceLoader::init):
(WebCore::ResourceLoader::isPortAllowed):
* Source/WebCore/loader/ResourceLoader.h:
* Source/WebCore/loader/SubframeLoader.cpp:
(WebCore::FrameLoader::SubframeLoader::loadSubframe):
* Source/WebCore/loader/SubresourceLoader.cpp:
(WebCore::SubresourceLoader::willSendRequestInternal):
* Source/WebCore/loader/cache/CachedResourceLoader.cpp:
(WebCore::CachedResourceLoader::requestResource):
* Tools/TestWebKitAPI/Tests/WebKitCocoa/Navigation.mm:
(TEST(WKNavigation, AllowResourceLoadFromBlockedPortWithCustomScheme)):
Canonical link: https://commits.webkit.org/302269@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
