Ticket #162 (closed enhancement: fixed)
When loading data for t:variable/@src fails, nothing happens in browser.
| Reported by: | bruno | Owned by: | jgou |
|---|---|---|---|
| Priority: | minor | Milestone: | 0.4 |
| Component: | modules/kauri-template | Version: | trunk |
| Keywords: | Cc: |
Description
I've noticed this a few times already with Firefox.
If you have a template which loads data using t:variable, and this fail, e.g. because the addressed resource does not exist, then nothing happens in the browser: the current page remains shown, giving the impression that everything that somehow no error happened. Most likely this is only the case when the t:variable is near the top of the template.
Have not looked closer into the origin of the problem, possibly a failure to reset the output, in which case the same problem will likely occur in other occasions as well.
Change History
comment:1 Changed 4 years ago by bruno
- Owner changed from mpo to jgou
- Component changed from -- unknown -- to modules/kauri-template
comment:2 Changed 4 years ago by bruno
The response Restlet sends to the browser in this case is:
HTTP/1.0 200 The request has succeeded Content-Type: text/html Date: Mon, 15 Dec 2008 15:36:50 GMT Accept-Ranges: bytes Server: Noelios-Restlet-Engine/1.2.snapshot Connection: close Transfer-Encoding: chunked HTTP/1.0 500 An exception occured writing the response entity Content-Type: text/html Date: Mon, 15 Dec 2008 15:36:50 GMT Accept-Ranges: bytes Server: Noelios-Restlet-Engine/1.2.snapshot Connection: close Transfer-Encoding: chunked
Thus double headers. It seems the first set of response headers was already flushed. Needs further investigation.
comment:3 Changed 4 years ago by bruno
I found out the source of the problem, it is a problem in Restlet:
http://restlet.tigris.org/issues/show_bug.cgi?id=687
The problem was that the Jetty connector was not detected, and hence not used, and the simple default server of Jetty isn't able to reset the response after the initial headers have been written.