-
Notifications
You must be signed in to change notification settings - Fork 202
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
RqHref.Base reads first line of header without checking format #445
Comments
@HDouss seems to be a valid bug, thanks |
@HDouss attached this issue to milestone "1.0" (let me know if this is wrong) |
@HDouss thanks for reporting! I topped your account for 15 mins, transaction 71676136 |
@Happy-Neko could you please pick this up? This article explains how we work. Any technical questions you may ask right here The cost of this task is 30 mins (this is exactly how much will be paid, not less not more), when the task is done |
@davvd I should anyway close this issue, right ? |
@Happy-Neko The pattern used assume that a "third part" of the request line is optional. I am not sure it is the case according to the specifications. The current implemented pattern will accept request lines like : |
@HDouss Protocol part is required per HTTP 1.1 specs. It is optional if we want to maintain backward compatibility with HTTP 1.0. |
@Happy-Neko Ok. Make sense. |
@davvd I will close the issue as the PR is merged and accepted. |
@Happy-Neko Please make a reference to the PR id. |
@Happy-Neko Thanks ! |
@ypshenychka please, check this issue for QA compliance, as per par.24 |
@davvd Quality is good here. |
@ypshenychka thank you |
@Happy-Neko 10 mins was added to the account of @ypshenychka (for QA review), in transaction 72638957; thanks, I just added 30 mins to your account, payment |
org.takes.rq.RqHref.Base
just reads first header and takes second element after space splitting :this.head().iterator().next().split(" ", 3)[1]
It should check if the header format satisfies HTTP specifications.
- `445-5323c196`/#473 (by Vladimir Maximenko)
The text was updated successfully, but these errors were encountered: