Google Git
Sign in
chromium / chromium / src.git / 51bac23ba8e802f9cabefe489936aa316c98316f
commit51bac23ba8e802f9cabefe489936aa316c98316f[log] [tgz]
authorKenichi Ishibashi <[email protected]>Thu Mar 18 10:05:17 2021
committerChromium LUCI CQ <[email protected]>Thu Mar 18 10:05:17 2021
treeb9e308065742c63f77d7b2afeaf9f7a5a87244d1
parent66e5c89ef9b8b21e1e7225552c49f442ed0d6cd8 [diff]
Plumb 103 responses from QuicHttpStream

This CL adds 1xx responses support to QuicChromiumClientStream, mainly
to plumb 103 Early Hints.

The basic approach is similar to quic::QuicSpdyClientStream. When
OnInitialHeadersComplete() is called, QuicChromiumClientStream parses
the ":status" pseudo-header then perform the followings:
* If status is invalid, reset the stream.
* Otherwise, if status is non-informational (>=200), treat the header as
  the final response.
* Otherwise, if status == 101, reset the stream.
* Otherwise, if status == 103, notify the corresponding handle that an
  Early Hints is available.
* Otherwise, ignore the informational response.

The handle (QuicChroimiumClientStream::Handle) delivers Early Hints to
the owner via ReadInitialHeaders(). In production code, the owner of the
handle is QuicHttpStream, which is used by HttpNetworkTransaction.

The reason the handle doesn't provide a separate method like
ReadEarlyHints() is that HttpNetworkTransaction handles Early Hints in
DoREadHeadersComplete(), which indirectly calls
QuicChromiumClientStream::Handle::ReadInitialHeaders().

Bug: 1096414

Change-Id: I1ba0c8d5f2fba39ee691d05e0363972ae9428bc0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2759798
Commit-Queue: Kenichi Ishibashi <[email protected]>
Reviewed-by: Bence Béky <[email protected]>
Cr-Commit-Position: refs/heads/master@{#864173}
5 files changed
tree: b9e308065742c63f77d7b2afeaf9f7a5a87244d1
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. cloud_print/
  13. codelabs/
  14. components/
  15. content/
  16. courgette/
  17. crypto/
  18. dbus/
  19. device/
  20. docs/
  21. extensions/
  22. fuchsia/
  23. gin/
  24. google_apis/
  25. google_update/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. jingle/
  32. media/
  33. mojo/
  34. native_client_sdk/
  35. net/
  36. pdf/
  37. ppapi/
  38. printing/
  39. remoting/
  40. rlz/
  41. sandbox/
  42. services/
  43. skia/
  44. sql/
  45. storage/
  46. styleguide/
  47. testing/
  48. third_party/
  49. tools/
  50. ui/
  51. url/
  52. weblayer/
  53. .clang-format
  54. .clang-tidy
  55. .eslintrc.js
  56. .git-blame-ignore-revs
  57. .gitattributes
  58. .gitignore
  59. .gn
  60. .vpython
  61. .vpython3
  62. .yapfignore
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. DEPS
  68. DIR_METADATA
  69. ENG_REVIEW_OWNERS
  70. LICENSE
  71. LICENSE.chromium_os
  72. OWNERS
  73. PRESUBMIT.py
  74. PRESUBMIT_test.py
  75. PRESUBMIT_test_mocks.py
  76. README.md
  77. WATCHLISTS
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure .

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.