You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
QUERY is a proposed new HTTP method type that is ideal for use in patch subset as it allows for a binary message body to be included while maintaining the cacheability and semantics of a GET request. This would allow us to avoid the use of POST requests.
QUERY is still a draft so we may have to wait for it to be finalized before fully depending on it in our specification. This issue is to track the addition of QUERY to the IFT spec once the QUERY spec is finalized.
In the meantime there are a a few questions about query that would be good to clarify:
Will range-requests work with QUERY? currently range requests are defined to only work with GET requests.
Will QUERY be considered a simple request and be exempt from CORS pre-flight requirements (this will likely need to be defined in the fetch specification).
The text was updated successfully, but these errors were encountered:
QUERY is a proposed new HTTP method type that is ideal for use in patch subset as it allows for a binary message body to be included while maintaining the cacheability and semantics of a GET request. This would allow us to avoid the use of POST requests.
QUERY is still a draft so we may have to wait for it to be finalized before fully depending on it in our specification. This issue is to track the addition of QUERY to the IFT spec once the QUERY spec is finalized.
In the meantime there are a a few questions about query that would be good to clarify:
The text was updated successfully, but these errors were encountered: