-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DefaultContentNegotiator should support wildcards #52
Comments
Works like a charm, tested on curl |
Thanks. I was in a dilemma if there's any need to support wildcard because people depending on the Accept header should specify one anyway. But it seemed like the right thing to do. |
I can make a release. It would be appreciated if you test this in your environment. I am in a totally different project now, away from servlet container like tomcat and using Play so cannot test this apart from playing with example project at home. If there is a bug, we can still release a bug fix later. |
We can do that, shouldn't be a problem. |
Are you guys also using ajax-compiler module? I am releasing now 1.25.4... |
Released, will be synced to maven central within a few hours. |
We're not using the ajax compiler AFAIK. |
Maven central sync complete: http://repo1.maven.org/maven2/pl/matisoft/spring-soy-view/1.25.4/ |
When the Accept header contains wildcard /, DefaultContentNegotiator should not try a literal match but return EQUAL instead.
The text was updated successfully, but these errors were encountered: