Bugzilla – Full Text Bug Listing
| Summary: | JS error on session timeout (Google Chrome) | ||
|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Michael Fröschen <michael.froeschen> |
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | bugs.eclipse.org, julian.fuerter |
| Version: | 3.2 | ||
| Target Milestone: | 3.4 | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: | https://git.eclipse.org/r/#/c/110220/ | ||
| Whiteboard: | |||
We're experiencing the same problem. But only since the latest Chrome Update '60.0.3112.113'. And '60.0.3112.090' Thanks for the bugfix. *** Bug 526806 has been marked as a duplicate of this bug. *** *** Bug 526806 has been marked as a duplicate of this bug. *** |
In other Browsers the RAP Client displays the error box if a session timeout occurs. That is not the case with Google Chrome. Instead the following Stacktrace is logged: Uncaught TypeError: Cannot read property 'indexOf' of undefined at Object._isJsonResponse (rap-client.js:62964) at Object._handleError (rap-client.js:62876) at rwt.remote.Request._error (rap-client.js:31494) at rwt.remote.Request._onReadyStateChange (rap-client.js:31531) at XMLHttpRequest.<anonymous> (rap-client.js:624) This can be reproduced by running the demo application with a small session timout setting (i used 15 seconds). After you wait out the timout and then click anywhere in the client, the mentioned stacktrace gets written into the JS console. The issue in this case is, that the client tries to get the content-type header by accessing it with a "wrong" string. ("Content-Type" is used, but it should be "content-type" in this case)