Closed vaadin-bot closed 8 years ago
Originally by @Peppe
Hi! Thanks for the report. Have you tested the same test against a non-TouckKit Vaadin application? VBrowserDetails comes from the Framework so it sounds like a problem in every Vaadin applicaiton.
Originally by @Artur-
As the stack trace suggests, this is a problem in TouchKit
at com.vaadin.addon.touchkit.settings.ApplicationCacheSettings.generateManifestFileName(ApplicationCacheSettings.java:85) ~[vaadin-touchkit-agpl-4.1.0.jar:4.1.0]
The framework does not assume that a user-agent header is present
String agent = request.getHeader("User-Agent");
if (agent != null) {
browserApplication = agent;
browserDetails = new VBrowserDetails(agent);
}
Originally by mvysny2
Wow, you guys are FAST! I am very sorry for bugging during Sunday :( Just verified that a plain Vaadin app seems unaffected:
curl -H "User-Agent:" http://localhost:8080
will just return the regular page of
... cut ...
<body>...<noscript>You have to enable javascript in your browser to use an application built with Vaadin.</noscript>
... cut ...
On the other hand, issuing that very same command against a Touchkit app, for example
curl -H "User-Agent:" https://aedict-online.eu
Will produce a nasty NPE stacktrace.
Originally by @alvarezguille
Patch was merged. Will be included in next maintenance release
Originally by mvysny2
Touchkit 4.1.0: Good day, I was trying the https://www.ssllabs.com SSL test on my https TouchKit-powered site, when I noticed the following stacktrace:
It seems that the VBrowserDetails fails if null is passed into its constructor.
Imported from https://dev.vaadin.com/ issue #19564