Skip to content
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

ContentNegotiatingViewResolver can not handle View implementations returning null as content type [SPR-6466] #11132

Closed
spring-projects-issues opened this issue Nov 28, 2009 · 1 comment
Assignees
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: bug A general bug
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

Oliver Drotbohm opened SPR-6466 and commented

The View interface allows getContentType() to return null. But Views returning null can not be handled by ContentNegotiatingViewResolver as it directly pipes the result of the call to getContentType() to MediaType.parseMediaType(..) which rejects null values passed.


Affects: 3.0 RC2

Referenced from: commits 73b54f4

@spring-projects-issues
Copy link
Collaborator Author

Arjen Poutsma commented

Should be fixed now

@spring-projects-issues spring-projects-issues added type: bug A general bug in: web Issues in web modules (web, webmvc, webflux, websocket) labels Jan 11, 2019
@spring-projects-issues spring-projects-issues added this to the 3.0 RC3 milestone Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: bug A general bug
Projects
None yet
Development

No branches or pull requests

2 participants