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.

Sign up for GitHub

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

Jump to bottom

KTOR-6851 Parsing Content-Length to Long instead of Int to prevent Nu… #4008

Merged
merged 3 commits into from Mar 28, 2024
Merged

KTOR-6851 Parsing Content-Length to Long instead of Int to prevent Nu… #4008

merged 3 commits into from Mar 28, 2024

Conversation

Stexxe
Copy link
Contributor

@Stexxe Stexxe commented Mar 28, 2024

@Stexxe Stexxe requested a review from e5l March 28, 2024 09:19
e5l
e5l approved these changes Mar 28, 2024
View reviewed changes
Copy link
Member

@e5l e5l left a comment

Choose a reason for hiding this comment

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

lgtm

@Stexxe Stexxe merged commit 5513dcf into main Mar 28, 2024
12 of 16 checks passed
@Stexxe Stexxe deleted the stexxe/nfe-cio branch March 28, 2024 11:47
e5l pushed a commit that referenced this pull request Apr 4, 2024
@Stexxe @e5l
KTOR-6851 Parsing Content-Length to Long instead of Int to prevent Nu… (
ccd8c67 
#4008)

* KTOR-6851 Parse Content-Length to Long instead of Int to prevent NumberFormatException for lengths more than Int.MAX_VALUE

(cherry picked from commit 5513dcf)
e5l pushed a commit that referenced this pull request Apr 5, 2024
@Stexxe @e5l
KTOR-6851 Parsing Content-Length to Long instead of Int to prevent Nu… (
182386a 
#4008)

* KTOR-6851 Parse Content-Length to Long instead of Int to prevent NumberFormatException for lengths more than Int.MAX_VALUE

(cherry picked from commit 5513dcf)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@e5l e5l e5l approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@Stexxe @e5l