DescriptionSupport HttpOnly cookie on Web Socket
Web Socket should send "HttpOnly" cookie when handshaking.
In WebKit/WebCore, WebSocketHandshake uses cookieRequestHeaderFieldValue() to
get cookies including HttpOnly cookie. However, Chrome doesn't trunk renderer
process, so we're not allowed to access HttpOnly cookie in WebCore.
Thus, we handle HttpOnly cookies in browser process.
Add SocketStreamJob as interface for protocol specific handling on
SocketStream.
WebSocketJob implements Web Socket specific handling. For now, it handles
cookies in Web Socket. It checks Web Socket handshake request message
from renderer process, and replaces Cookie: header to include HttpOnly cookies.
It also checks Web Socket handshake response message, sets cookies if any,
and strips Set-Cookie: header, so that renderer process couldn't see
Set-Cookie: header.
BUG=35660
TEST=net_unittests and layout_tests passes
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=40250
Patch Set 1 #
Total comments: 6
Patch Set 2 : Use SCOPED_TRACE #
Total comments: 12
Patch Set 3 : Use CookiePolicy #
Total comments: 4
Patch Set 4 : fix darin's comment #Messages
Total messages: 9 (0 generated)
|