Skip to content

Update to handle 501 again when the HTTP verb is not handled by prime-mvc - #87

Merged
robotdan merged 3 commits into
mainfrom
degroff/update_for_501
Aug 13, 2025
Merged

Update to handle 501 again when the HTTP verb is not handled by prime-mvc#87
robotdan merged 3 commits into
mainfrom
degroff/update_for_501

Conversation

@robotdan

Copy link
Copy Markdown
Contributor

Summary

We used to handle 501 before we moved to java-http because we had to parse the http verb into a servlet enum.

We can now handle any value w/out explosion, but we still only map out standard methods in the DefaultActionConfigurationBuilder.

So this is just to fix the error to be more accurate, which is what we used to do.

…parse the http verb into a servlet enum.

We can now handle any value w/out explosion, but we still only map out standard methods in the DefaultActionConfigurationBuilder.

So this is just to fix the error to be more accurate, which is what we used to do.
Comment thread src/main/java/org/primeframework/mvc/action/DefaultActionMappingWorkflow.java Outdated
…ngWorkflow.java

Co-authored-by: Mark Manes <mark.manes@fusionauth.io>
@robotdan
robotdan merged commit 399156b into main Aug 13, 2025
@robotdan
robotdan deleted the degroff/update_for_501 branch August 13, 2025 16:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants