-
Notifications
You must be signed in to change notification settings - Fork 103
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
Add message streaming mode #1012
Closed
Closed
Changes from all commits
Commits
Show all changes
26 commits
Select commit
Hold shift + click to select a range
9c5b992
cfg: add parse long and unify error messages on parse integer errors
vankoven ff5d793
fix incorrect spelling
vankoven 2bfaeaf
restrict client rmem size
vankoven a1639f0
export sysctl_tcp_moderate_rcvbuf in kernel
vankoven 989dfb4
add missing state in TCP debug
vankoven fd67725
Add client|server_msg_buffering configuration directive
vankoven 22481bb
move http parser functions to separate header
vankoven 53161dd
move parser to connetion, don't allocate it for each incoming message
vankoven b2c643d
use standart bitops functions for message flags.
vankoven 7fa3d1a
Correct more spelling mistakes
vankoven b5bb500
Remove duplicated namings for connection flags
vankoven 1f3542b
move comment to single line
vankoven 8846486
remove extra type conversions
vankoven 9d5a3f0
TODO client_responses_rmem
vankoven 3f9693f
Remove TFW_HTTP_SUSPECTED flag
vankoven cd02fcf
unify tfw_http_cli_error_resp_and_log code
vankoven 8ad0e02
reformat tfw_http_req_process to simplify connection management
vankoven 8a8a20b
Add todo for tfw_http_cli_error_resp_and_log
vankoven 9921c7b
reformat tfw_http_resp_process to simplify connection management
vankoven 6a613ce
correctly delist request on response parsing errors
vankoven 63054ab
TFW_HTTP_FSM_LOCAL_RESP_FILTER is egress state, don't mix up with ing…
vankoven 54c8ceb
correct spelling mistakes
vankoven e8e111b
don't break logged line
vankoven f696de7
parser: add helper function to allow processing of streamed parts
vankoven 1df138b
unify tfw_http_cli_error_resp_and_log code
vankoven b51dcca
Move msg_sent to TFW_CONN_COMMON
vankoven File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unfortunately, the PR is still unfinished and I can not run Tempesta with error configuration to see what it prints, but it seems that now it just prints that it can not parse some invalid integer, w/o localization which exactly configuration option causes the problem. If a user specifies a string for several configuration options and only one of them is actually an integer, then the user must check documentation for all the options and that's not user friendly. I think the unification of error messages in 71043eb is wrong.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't really like how Tempesta complains about parsing errors, e.g. for line
server 127.0.0.1:8080 conns_n=1a;
:On master:
On my branch:
As for me, last option is more verbose. Yes, that commit made the output less verbose for some options. But before changes it looked ugly: every directive has it's own unique error message, error processing is also unique for every directive. Some errors described very good, while descriptions for others are completely missed. My variant is much easier to support.
The thing I completely dislike in parsing errors is reversed error message. Ideal message for me is below:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree, the change is actually good since we still have
And yes,
would look much better.