Supported HTTP request methods

The current release of WFM contains several new features that rely on HTTP DELETE and PUT methods. To ensure uninterrupted functionality post-upgrade, verify that your WFM environment does not block application requests from these methods.

Some infrastructure configurations might block the HTTP DELETE and PUT request types. When these HTTP request methods are blocked in your environment, you might encounter unexpected issues post-upgrade.

These examples show how different layers in your environment configuration might block the supported request methods.
  • Wildfly Undertow Subsystem Configuration
  • Editing Apache config, .htcaccess, or using LimitExcept Directive on Apache HTTP Server (Reverse Proxy or Frontend)
  • Web Application Firewall (WAF)
  • Load Balance/API Gateways such as HAProxy, NGINX, or Envoy
  • Firewall with Deep Packet Inspection
  • Host-based Intrusion Prevention Systems

It is the responsibility of your on-premises system administrator to ensure that the specified HTTP methods are not blocked within the environment.

If you are upgrading to version 2024.x or later, you must ensure that your environment is configured to support these HTTP methods. This configuration helps prevent service disruptions and facilitates a smooth transition to the latest version.