Misleading Communication Problem (session timeout).
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 717
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 3
Description
Originally by lstrzelecki
In portal (Liferay) environment when http session closes, then displays Communication Problem notification. In standard environment (only servlet container) is shown Session Timeout notification.
Could it behave in same way on this environments?
Vaadin 6.8.3
Liferay 6.0.5
Imported from https://dev.vaadin.com/ issue #9694
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Java code that handles session expiration and chooses between the Communication Problem and Session Timeout notifications. Compare behavior in the Liferay portal and standard servlet-container environments; done when an expired HTTP session produces the same Session Timeout notification in both.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100