Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't uppercase HTTP verb in parser #3233

Merged
merged 2 commits into from
Sep 2, 2018
Merged

Conversation

asvetlov
Copy link
Member

@asvetlov asvetlov commented Sep 1, 2018

RFC 7320 sec. 3.1.1:

The request method is case sensitive

Copy link
Member

@webknjaz webknjaz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perfect. Now it's more RFC-compliant :)

@codecov-io
Copy link

Codecov Report

Merging #3233 into master will decrease coverage by <.01%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #3233      +/-   ##
==========================================
- Coverage   98.07%   98.07%   -0.01%     
==========================================
  Files          43       43              
  Lines        7857     7856       -1     
  Branches     1354     1354              
==========================================
- Hits         7706     7705       -1     
  Misses         59       59              
  Partials       92       92
Impacted Files Coverage Δ
aiohttp/http_parser.py 98.06% <ø> (-0.01%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b7206f4...73d6530. Read the comment docs.

@asvetlov asvetlov merged commit 7b71302 into master Sep 2, 2018
@asvetlov asvetlov deleted the no-uppercase-http-verb branch September 2, 2018 06:47
@lock
Copy link

lock bot commented Oct 28, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a [new issue] for related bugs.
If you feel like there's important points made in this discussion, please include those exceprts into that [new issue].
[new issue]: https://github.com/aio-libs/aiohttp/issues/new

@lock lock bot added the outdated label Oct 28, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Oct 28, 2019
@psf-chronographer psf-chronographer bot added the bot:chronographer:provided There is a change note present in this PR label Oct 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bot:chronographer:provided There is a change note present in this PR outdated
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants