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
Lava Webhook of Method PUT or PATCH don't resolve #3277
Comments
Admittedly, I never tested this with PUT and PATCH specifically. I just included those verbs as a "why not". I wonder if IIS is internally trying to handle those rather than letting the web hook handle it. |
@cabal95 are you able to look at this? |
Yes, I'll take a look and see if I can verify what the core issue is. |
It looks like this is an issue at the web.config level. Or more specifically, at the "server" level web.config. The default handler mapping for
To enable for testing:
edit: picture I forgot: |
Is not having support for PUT/PATCH a deal since Lava can't update data? |
It's not a huge issue, but the Lava Webhooks have their own Entity Command enabling, so they can use A fourth option, would be to convert the attribute to be a plain Text attribute. This shouldn't cause any backwards compatibility issues. It would require the user to specifically put in the verb name (GET, POST, etc.) - though we could make it default to |
Prerequisites
Description
If you create a lava webhook with a method of PUT or PATCH, it does not seem to add the route. If you switch it to POST, it works fine.
Steps to Reproduce
Expected behavior:
PATCH and PUT routes should be defined.
Actual behavior:
Rock doesn't know they exist.
Versions
The text was updated successfully, but these errors were encountered: