Hi Natascia,
It's also worth noting that, by default, the "r" (read) permission in ACL allows PATCH operation. If you want to independently control use of PATCH, you can assign it to a different permission bit in the Reverse Proxy configuration.
Jon.
------------------------------
IAM Jon
------------------------------
Original Message:
Sent: Thu June 16, 2022 03:55 PM
From: Scott Exton
Subject: HTTP PATCH
Natascia,
WebSEAL is able to forward the PATCH request onto junctioned servers, but does not support the PATCH method when accessing a local junction.
The 'http-method-disabled-remote' configuration entry within the '[server]' stanza lists the methods for which WebSEAL will return a 501. I suspect that you might have the 'PATCH' method listed here, and if so, it should be removed.
If you are still getting a 501 after updating the 'http-method-disabled-remote' configuration entry I would then suggest that you enable to pdweb.snoop tracing to check that the 501 is not coming from the junctioned server.
I hope that this helps.
Scott A. Exton
Senior Software Engineer
Chief Programmer - IBM Security Verify Access
IBM Master Inventor
Original Message:
Sent: 6/16/2022 10:19:00 AM
From: Natascia Roia
Subject: HTTP PATCH
Hi all,
is there a configuration to allow the use of the HTTP PATCH method? It's supported by the ISVA proxies? The HTTP response now it 501
Thank you,
Natascia
------------------------------
Natascia Roia
------------------------------