Markus KARG

As we are late with 3.1, I think deferring to 4.0 is the right choice.

At the moment I do not see any reason for a second Jenkins job. I can look into extending the existing one, but unfortunately this will take a while as...

@jansupol @spericas @andymc12 @chkal @arjantijms Please review and vote on this PR. Thanks.

> This is actually a big change. Up until now, Jakarta REST referred to [HTTP 1.1 RFC 2616](https://datatracker.ietf.org/doc/html/rfc2616). This PR basically says [RFC 7231](https://datatracker.ietf.org/doc/html/rfc7231) should be used instead. This is...

@jelemux Can you please fix the conflicts? Thanks!

AFAIK @jelemux is working on this one.

For security reasons, this would be an interesting option. Filters could use the sender's IP to detect if the sender is entitled for the call. For example, people might like...

Now that working on 4.0 is in progress, we should continue this discussion thread.

Do you like to file a PR containing all needed changes to API, spec, tests and TCK? That would be terrific! :-)

(I am the original reporter of this issue) I think we could address this in 3.1, and if nobody chimes in, I will provide a PR. Before that, we should...