With regards to the intermediary issue Joakim mentioned, a non-standard
but common solution is to send a POST with an X-HTTP-Method-Override header.
When the header is present, its value is simply used instead of the
request method, the specifics of which depend on your webapp's request
processing logic (i.e. this isn't a Jetty feature; it requires code to
be written, but hopefully only two lines in a single location).
Obviously this is only feasible when you can alter/instruct the client
to send the request in this way, but it can help when you have an API
used by developers stuck behind restrictive corporate firewalls.
_______________________________________________
jetty-users mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://www.eclipse.org/mailman/listinfo/jetty-users
