Summary

The HTTP QUERY method (RFC 10008) provides a standardized way to perform safe, idempotent query operations while allowing a request body, addressing a long-standing limitation of GET.

https://www.rfc-editor.org/info/rfc10008/

https://tykok.medium.com/the-new-http-method-query-d1dc3efc35c4

While ASP.NET Core applications can implement support for QUERY, developers deploying to Optimizely DXP also depend on the surrounding platform and infrastructure.

Request

Could Optimizely publish official guidance regarding support for the HTTP QUERY method in DXP?

Specifically, it would be helpful to clarify:

• Is QUERY currently supported throughout the DXP infrastructure?
• If not, which components prevent support (Cloudflare, WAF, load balancers, Azure App Service, proxies, etc.)?
• Are there any security considerations specific to QUERY that developers should be aware of?
• Will QUERY be treated similarly to GET regarding safe/idempotent semantics where applicable?
• Is support on the product roadmap, or is it considered out of scope?
• If there is no current support, what is the recommended approach for developers who would otherwise benefit from QUERY?

Why this matters

Many APIs expose complex search and filtering operations that naturally fit a safe, idempotent request but exceed the practical limitations of GET query strings.

The QUERY method provides a standards-based solution to this problem. As more frameworks begin supporting it, developers will naturally want to know whether Optimizely DXP fully supports the method before adopting it.

Even if official support is not yet planned, having clear documentation describing the current state and any platform limitations would help developers make informed architectural decisions.

Thank you for considering publishing official guidance.