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

UnsupportedBrowserHandler doesn't include Content-Type-Header in response #7936

Closed
StefanPenndorf opened this issue Mar 30, 2020 · 0 comments · Fixed by #8803
Closed

UnsupportedBrowserHandler doesn't include Content-Type-Header in response #7936

StefanPenndorf opened this issue Mar 30, 2020 · 0 comments · Fixed by #8803
Assignees

Comments

@StefanPenndorf
Copy link

The error page generated by UnsupportedBrowserHandler doesn't add a Content-Type header. Thus chrome offers the page for download instead of displaying the error message.

Reproduce:

Can be fixed by adding

        response.setContentType("text/html charset=utf-8");

Affected Versions: all (even UnsupportedBrowserHandler in Vaadin 8 seems affected although I found the bug evaluating a Vaadin 14 application).

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

Successfully merging a pull request may close this issue.

2 participants