Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
There should be a way to avoid Vaadin reliance on cookies
See original GitHub issueSee this ticket : https://github.com/vaadin/framework/issues/814
It should be possible to use Vaadin app without any reliance on cookies.
Vaadin app as any other Java servlet app set JSESSIONID cookie on first server response to track an HTTP session.
Vaadin relies on HTTP session servlet mechanism which relies on this cookie.
Sometimes cookies don’t work: e.g. in embedding applications ( see https://github.com/vaadin/flow/issues/5769).
We should provide a way to configure the app do not rely on cookies and somehow track the session id in every request/response .
That will allow to make app working even if cookies are not supported for some reasons.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:4
- Comments:30 (22 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
In this case as we claim that we have embedding support and did not already explicitly mention that it is not supported cross domain in Safari, I’m willing to rule this out as an bug as we have a good idea how to fix this for those users who are relying to get this fixed.
What about support of the URL-based session tracking? Vaadin doesn’t support this at the moment - it will endlessly reload the page and eventually will give up stating “Cookies disabled”. SSL session tracking is unreliable as discussed above. Sounds to me that cookie-based session tracking is the only way. I’ve added docs rgd this to https://mvysny.github.io/the-dreaded-vaadin-session-has-expired/