From 2800b21feaebe8c561e9d81167020323bce963f6 Mon Sep 17 00:00:00 2001
From: interp <interp>
Date: Sun, 3 Nov 2002 14:37:53 +0000
Subject: [PATCH] Browser caching may be a reason for wrong servlet request.
 Tell them about it.

---
 scheme/httpd/surflets/surflet-handler.scm | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/scheme/httpd/surflets/surflet-handler.scm b/scheme/httpd/surflets/surflet-handler.scm
index 1c3bd2b..3665f09 100644
--- a/scheme/httpd/surflets/surflet-handler.scm
+++ b/scheme/httpd/surflets/surflet-handler.scm
@@ -205,14 +205,14 @@
 	    http-status/bad-request req
 	    (format #f 
 		    "<br>
-<p>There may be several reasons, why your request was denied:
+<p>There may be several reasons, why your request for a servlet was denied:
 <ul>
 <li>The servlet does not accept any requests any more.</li>
 <li>The servlet URL has timed out.</li>
 <li>You URL is illformed.</li>
 </ul>
 </p>
-<p>In any case, you may try to restart the servlet from the <a href=\"~a\">beginning</a></p>"
+<p>In any case, you may try to restart the servlet from the <a href=\"~a\">beginning</a>. Your browser may also have cached an old instance of this servlet. In this case, try to reload the page.</p>"
 		    (resume-url-servlet-name path-string)))))
 	(lookup-continuation-table
 	  (lambda (instance continuation-table continuation-id)