-
Notifications
You must be signed in to change notification settings - Fork 4k
Validate 'next-action' header format in server action requests #3523
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
base: main
Are you sure you want to change the base?
Conversation
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
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.
Pull Request Overview
This PR implements validation for the 'next-action' header format in server action requests to ensure it meets the expected format before processing. The validation checks that the header matches a specific pattern (1-byte hex string followed by a 20-byte SHA1 hash).
- Adds regex validation to check 'next-action' header format against the expected 42-character hex pattern
- Returns early 400 response for invalid header formats
- Restructures the existing server action validation logic to accommodate the new header format check
Implement validation for the 'next-action' header format to ensure it meets the expected criteria before processing server action requests. This change enhances request handling by rejecting invalid formats early.