-
Notifications
You must be signed in to change notification settings - Fork 504
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
MaxInitialLineSize parameter is not set from maxInitialLineKB config value #2393
Closed
1 of 2 tasks
Comments
koiuo
added a commit
to koiuo/linkerd
that referenced
this issue
May 27, 2020
MaxInitialLineSize parameter is not set from the config. This appears to be a regression in 1.7.x This commit adds test case to demonstrate the issue and a fix Fixes linkerd#2393 Signed-off-by: Dmytro Kostiuchenko <[email protected]>
koiuo
added a commit
to koiuo/linkerd
that referenced
this issue
May 27, 2020
MaxInitialLineSize parameter is not set from the config. This appears to be a regression in 1.7.x This commit adds test case to demonstrate the issue and a fix Fixes linkerd#2393 Signed-off-by: Dmytro Kostiuchenko <[email protected]>
cpretzer
pushed a commit
that referenced
this issue
May 28, 2020
MaxInitialLineSize parameter is not set from the config. This appears to be a regression in 1.7.x This commit adds test case to demonstrate the issue and a fix Fixes #2393 Signed-off-by: Dmytro Kostiuchenko <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue Type:
What happened:
maxInitialLineKB
config value is ignored by linkerd, resulting in 414 for request with long URLsWhat you expected to happen:
maxInitialLineKB
value is used to setMaxInitialLineSize
parameter for the routerHow to reproduce it (as minimally and precisely as possible):
set
maxInitialLineKB
to a 64KiB and submit a request with request line > 4KiB (default value for themaxInitialLineKB
Anything else we need to know?:
This seems to be a regression in 1.7.x
Environment:
The text was updated successfully, but these errors were encountered: