RESOLVED FIXED 105738
Remove Key3 & Challenge Response from WebInspector-NetworkPanel-HeaderTab for websocket
https://bugs.webkit.org/show_bug.cgi?id=105738
Summary Remove Key3 & Challenge Response from WebInspector-NetworkPanel-HeaderTab for...
pdeng6
Reported 2012-12-24 23:55:32 PST
Since Key3 and Challenge response field are removed during IETF-websocket spec evolution, and corresponding interfaces are not invoked in current websocket implementation, I think remove them from web-inspector is reason-able. @Toyoshima san, I guess they won't be back in future, am I right? origin bug from https://code.google.com/p/chromium/issues/detail?id=142280
Attachments
Key3 and Challenge Response fileds to be removed (89.16 KB, image/png)
2012-12-25 06:14 PST, pdeng6
no flags
Patch (10.71 KB, patch)
2012-12-25 06:22 PST, pdeng6
no flags
Patch (14.32 KB, patch)
2013-01-14 22:19 PST, pdeng6
no flags
Patch (14.54 KB, patch)
2013-01-15 00:32 PST, pdeng6
no flags
Takashi Toyoshima
Comment 1 2012-12-25 00:25:12 PST
Yes. It's time to remove these obsolete fields. Now that all WebKit ports migrate to the latest WebSocket protocol spec, RFC 6455, these fields are not used forever.
pdeng6
Comment 2 2012-12-25 00:31:17 PST
(In reply to comment #1) > Yes. It's time to remove these obsolete fields. > Now that all WebKit ports migrate to the latest WebSocket protocol spec, RFC 6455, these fields are not used forever. thanks :), I will prepare a patch.
pdeng6
Comment 3 2012-12-25 06:14:22 PST
Created attachment 180711 [details] Key3 and Challenge Response fileds to be removed
pdeng6
Comment 4 2012-12-25 06:22:28 PST
pdeng6
Comment 5 2012-12-28 04:43:52 PST
@Pavel, could you pelase help review this patch? thanks :) Pan
Pavel Feldman
Comment 6 2012-12-28 04:53:46 PST
(In reply to comment #1) > Yes. It's time to remove these obsolete fields. > Now that all WebKit ports migrate to the latest WebSocket protocol spec, RFC 6455, these fields are not used forever. Could you clarify whether ports have migrated to the latest protocol? Any new fields need to be inspected? Why are these still in the WebCore APIs? I would imagine that when they are removed, inspector's code will get fixed automatically.
Li Yin
Comment 7 2013-01-14 21:21:05 PST
See https://bugs.webkit.org/show_bug.cgi?id=88620 hixie76 protocol related implementation should be deleted. Hi pan, Could you please delete Key3 related codes in WebCore also?
Takashi Toyoshima
Comment 8 2013-01-14 22:13:52 PST
Sorry, I missed the comment #6. Yes, as Li said, old protocol doesn't work now, then all ports have no choice to use old protocol in WebKit. Issue 88620 removed major parts of old protocol implementation. But it wasn't perfect. Removing other hixie76 implementation looks fine. Please git grep with 'useHixie76Protocol' in WebCore. Also layout tests in http/tests/websocket/tests/hixie76 can be removed. Deng: If you don't have a time to clean them up, please let me know. I'll do. Thanks,
pdeng6
Comment 9 2013-01-14 22:19:51 PST
pdeng6
Comment 10 2013-01-14 23:31:59 PST
(In reply to comment #8) > Sorry, I missed the comment #6. > > Yes, as Li said, old protocol doesn't work now, then all ports have no choice to use old protocol in WebKit. > Issue 88620 removed major parts of old protocol implementation. But it wasn't perfect. > Removing other hixie76 implementation looks fine. > > Please git grep with 'useHixie76Protocol' in WebCore. > Also layout tests in http/tests/websocket/tests/hixie76 can be removed. > > Deng: > If you don't have a time to clean them up, please let me know. I'll do. > > Thanks, thanks, obsoleted fields in WebCore are removed in this patch, I think it is clean as my grep. :) @tkent, @Pavel, could you please review this change? thanks Pan
Kent Tamura
Comment 11 2013-01-14 23:35:35 PST
Comment on attachment 182704 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=182704&action=review > Source/WebCore/ChangeLog:5 > + Need the bug URL (OOPS!). OOPS! Remove this line. > Source/WebCore/ChangeLog:12 > + No new tests (OOPS!). OOPS!. Please replace this OOPS! with a reason why the patch has no tests. > Source/WebCore/ChangeLog:31 > + * Modules/websockets/WebSocketHandshakeRequest.cpp: > + * Modules/websockets/WebSocketHandshakeRequest.h: > + (WebSocketHandshakeRequest): > + * Modules/websockets/WebSocketHandshakeResponse.cpp: > + * Modules/websockets/WebSocketHandshakeResponse.h: > + (WebSocketHandshakeResponse): > + * inspector/Inspector.json: > + * inspector/InspectorResourceAgent.cpp: > + (WebCore): > + (WebCore::InspectorResourceAgent::willSendWebSocketHandshakeRequest): > + (WebCore::InspectorResourceAgent::didReceiveWebSocketHandshakeResponse): > + * inspector/front-end/NetworkManager.js: > + (WebInspector.NetworkDispatcher.prototype.webSocketWillSendHandshakeRequest): > + (WebInspector.NetworkDispatcher.prototype.webSocketHandshakeResponseReceived): > + * inspector/front-end/RequestHeadersView.js: > + (WebInspector.RequestHeadersView.prototype._refreshRequestHeaders): > + (WebInspector.RequestHeadersView.prototype._refreshResponseHeaders): > + (WebInspector.RequestHeadersView.prototype._refreshHeaders): Please write per-file / per-function comments as possible.
pdeng6
Comment 12 2013-01-15 00:32:34 PST
pdeng6
Comment 13 2013-01-15 00:35:00 PST
(In reply to comment #11) > (From update of attachment 182704 [details]) > View in context: https://bugs.webkit.org/attachment.cgi?id=182704&action=review > > > Source/WebCore/ChangeLog:5 > > + Need the bug URL (OOPS!). > > OOPS! Remove this line. > Done, thanks. > > Source/WebCore/ChangeLog:12 > > + No new tests (OOPS!). > > OOPS!. Please replace this OOPS! with a reason why the patch has no tests. > thanks, done. > > Source/WebCore/ChangeLog:31 > > + * Modules/websockets/WebSocketHandshakeRequest.cpp: > > + * Modules/websockets/WebSocketHandshakeRequest.h: > > + (WebSocketHandshakeRequest): > > + * Modules/websockets/WebSocketHandshakeResponse.cpp: > > + * Modules/websockets/WebSocketHandshakeResponse.h: > > + (WebSocketHandshakeResponse): > > + * inspector/Inspector.json: > > + * inspector/InspectorResourceAgent.cpp: > > + (WebCore): > > + (WebCore::InspectorResourceAgent::willSendWebSocketHandshakeRequest): > > + (WebCore::InspectorResourceAgent::didReceiveWebSocketHandshakeResponse): > > + * inspector/front-end/NetworkManager.js: > > + (WebInspector.NetworkDispatcher.prototype.webSocketWillSendHandshakeRequest): > > + (WebInspector.NetworkDispatcher.prototype.webSocketHandshakeResponseReceived): > > + * inspector/front-end/RequestHeadersView.js: > > + (WebInspector.RequestHeadersView.prototype._refreshRequestHeaders): > > + (WebInspector.RequestHeadersView.prototype._refreshResponseHeaders): > > + (WebInspector.RequestHeadersView.prototype._refreshHeaders): > > Please write per-file / per-function comments as possible. major comments added, thanks :)
Kent Tamura
Comment 14 2013-01-15 01:19:15 PST
Comment on attachment 182712 [details] Patch Looks good.
WebKit Review Bot
Comment 15 2013-01-15 17:50:02 PST
Comment on attachment 182712 [details] Patch Clearing flags on attachment: 182712 Committed r139814: <http://trac.webkit.org/changeset/139814>
WebKit Review Bot
Comment 16 2013-01-15 17:50:06 PST
All reviewed patches have been landed. Closing bug.
Takashi Toyoshima
Comment 17 2013-01-15 21:06:36 PST
Pan, thank you for fixing this issue.
pdeng6
Comment 18 2013-01-15 21:44:17 PST
(In reply to comment #17) > Pan, thank you for fixing this issue. you are welcome :)
Note You need to log in before you can comment on or make changes to this bug.