[XrdNet and XrdHttp] Scitag min and max value change #2139
Merged
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.
Hi @abh3 ,
I took a bit of time to work on adapting the packet marking to comply with the specification where the
scitag.flow
has to have values between 65 and 65535.I did two commits. The first one is changing the min and max values that a scitag can have and that modifies the
XrdHttp
part to check the validity of the scitag value given by the user.The second one also touches the configuration of the scitag configuration from a JSON file (taking into account min and max values). I also modified the validation of the PMark handle where a scitag=0 will only be valid for HTTP-TPC (according to the specs). For other protocols, the scitag given by the user will have to be between 65 and 65535, otherwise the traffic will not be tagged.
Thanks for your review!
Cheers,
Cedric