⚠ Archived content — this site is no longer maintained.   Current WebKit documentation is at docs.webkit.org.

Changeset 276136 in webkit


Ignore:
Timestamp:
Apr 16, 2021, 7:41:11 AM (5 years ago)
Author:
Carlos Garcia Campos
Message:

[SOUP] Show resource priority and remote IP in the inspector
https://bugs.webkit.org/show_bug.cgi?id=224660

Reviewed by Adrian Perez de Castro.

  • NetworkProcess/soup/NetworkDataTaskSoup.cpp:

(WebKit::toNetworkLoadPriority):
(WebKit::NetworkDataTaskSoup::didGetHeaders):
(WebKit::NetworkDataTaskSoup::networkEvent):

Location:
trunk/Source/WebKit
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • trunk/Source/WebKit/ChangeLog

    r276125 r276136  
     12021-04-16  Carlos Garcia Campos  <cgarcia@igalia.com>
     2
     3        [SOUP] Show resource priority and remote IP in the inspector
     4        https://bugs.webkit.org/show_bug.cgi?id=224660
     5
     6        Reviewed by Adrian Perez de Castro.
     7
     8        * NetworkProcess/soup/NetworkDataTaskSoup.cpp:
     9        (WebKit::toNetworkLoadPriority):
     10        (WebKit::NetworkDataTaskSoup::didGetHeaders):
     11        (WebKit::NetworkDataTaskSoup::networkEvent):
     12
    1132021-04-16  Youenn Fablet  <youenn@apple.com>
    214
  • trunk/Source/WebKit/NetworkProcess/soup/NetworkDataTaskSoup.cpp

    r276021 r276136  
    969969}
    970970
     971static WebCore::NetworkLoadPriority toNetworkLoadPriority(SoupMessagePriority priority)
     972{
     973    switch (priority) {
     974    case SOUP_MESSAGE_PRIORITY_VERY_LOW:
     975    case SOUP_MESSAGE_PRIORITY_LOW:
     976        return WebCore::NetworkLoadPriority::Low;
     977    case SOUP_MESSAGE_PRIORITY_NORMAL:
     978        return WebCore::NetworkLoadPriority::Medium;
     979    case SOUP_MESSAGE_PRIORITY_HIGH:
     980    case SOUP_MESSAGE_PRIORITY_VERY_HIGH:
     981        return WebCore::NetworkLoadPriority::High;
     982    }
     983
     984    return WebCore::NetworkLoadPriority::Unknown;
     985}
     986
    971987void NetworkDataTaskSoup::didGetHeaders()
    972988{
     
    9941010            requestHeaders.set(String(headerName), String(headerValue));
    9951011        m_networkLoadMetrics.requestHeaders = WTFMove(requestHeaders);
     1012
     1013        m_networkLoadMetrics.priority = toNetworkLoadPriority(soup_message_get_priority(m_soupMessage.get()));
    9961014    }
    9971015
     
    11921210        break;
    11931211    case G_SOCKET_CLIENT_CONNECTED:
     1212        if (shouldCaptureExtraNetworkLoadMetrics() && G_IS_SOCKET_CONNECTION(stream)) {
     1213            GRefPtr<GSocketAddress> address = adoptGRef(g_socket_connection_get_remote_address(G_SOCKET_CONNECTION(stream), nullptr));
     1214            if (G_IS_INET_SOCKET_ADDRESS(address.get())) {
     1215                GUniquePtr<char> ipAddress(g_inet_address_to_string(g_inet_socket_address_get_address(G_INET_SOCKET_ADDRESS(address.get()))));
     1216                m_networkLoadMetrics.remoteAddress = makeString(ipAddress.get(), ':', g_inet_socket_address_get_port(G_INET_SOCKET_ADDRESS(address.get())));
     1217            }
     1218        }
    11941219        // Web Timing considers that connection time involves dns, proxy & TLS negotiation...
    1195         // so we better pick G_SOCKET_CLIENT_COMPLETE for connectEnd
     1220        // so we better pick G_SOCKET_CLIENT_COMPLETE for connectEnd.
    11961221        break;
    11971222    case G_SOCKET_CLIENT_PROXY_NEGOTIATING:
Note: See TracChangeset for help on using the changeset viewer.