Skip to content
This repository has been archived by the owner on Jan 21, 2020. It is now read-only.

How to overcome limitations of GET? (X-HTTP-Method-Override?) #175

Open
jdukleth opened this issue Aug 19, 2016 · 4 comments
Open

How to overcome limitations of GET? (X-HTTP-Method-Override?) #175

jdukleth opened this issue Aug 19, 2016 · 4 comments

Comments

@jdukleth
Copy link

jdukleth commented Aug 19, 2016

Is there a method in place to overcome GET limitations? For example, browsers/Apache have a maximum character limit on query strings. The ability to send POST but use GET as the overriden method is desired.

Sending a X-HTTP-Method-Override header is the suggested standard that many APIs support. (Google is behind this). I have not found this or any other workaround in Apigility.

@jbh
Copy link

jbh commented Aug 22, 2016

+1

@Wilt
Copy link

Wilt commented Aug 23, 2016

I made a PR for this feature.
I think enabling this listener should be optional, feels not good to connect such a feature by default to the application so I connected the listener depending on a x_http_method_override_enabled key in the config.

Not sure exactly on what is a valid priority value for this listener. I would say as early as possible, currently set to -40 to be triggered before all other zf-campus onRoute listeners, but might earlier might be even better. I added a TODO to check this value...

@snapshotpl
Copy link
Contributor

@weierophinney
Copy link
Member

This repository has been closed and moved to laminas-api-tools/api-tools; a new issue has been opened at laminas-api-tools/api-tools#18.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants