Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #64926, comment 11


Ignore:
Timestamp:
03/26/2026 01:03:36 PM (3 months ago)
Author:
zieladam
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #64926, comment 11

    initial v1  
    1 @dsmy would you be willing to share more information about your use-case? While I don't have enough context off-hand to comment on possible solutions, I'm thinking that it is weird there is no historical solution for this. I wonder whether the REST API was intended for handling complex inputs via GET requests, or was the intention to always use POST. Is it just a documentation issue? POST requests are not subject to HTTP caching, for example, which wouldn't make sense for  uniquely generated pages parametrized by complex JSON structures. POST requests also behave differently under CORS etc. etc. Knowing more about your project would be a very helpful framing for this discussion.
     1@dsmy would you be willing to share more information about your use-case? While I don't have enough context off-hand to comment on possible solutions, I'm thinking that it is weird there is no historical ticket for this.
     2
     3I wonder whether the REST API was intended for handling complex inputs via GET requests, or was the intention to always use POST. Is it just a documentation issue? POST requests are not subject to HTTP caching, for example, which wouldn't make sense for  uniquely generated pages parametrized by complex JSON structures. POST requests also behave differently under CORS etc. etc. Knowing more about your project would be a very helpful framing for this discussion.