scsh-conservatory
/
sunet
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Browser caching may be a reason for wrong servlet request. Tell them 

about it.
This commit is contained in:
interp 2002-11-03 14:37:53 +00:00
parent 7b5cf03385
commit 2800b21fea
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
scheme/httpd/surflets/surflet-handler.scm
View File

@ -205,14 +205,14 @@
http-status/bad-request req http-status/bad-request req
(format #f (format #f
"<br> "<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> <ul>
<li>The servlet does not accept any requests any more.</li> <li>The servlet does not accept any requests any more.</li>
<li>The servlet URL has timed out.</li> <li>The servlet URL has timed out.</li>
<li>You URL is illformed.</li> <li>You URL is illformed.</li>
</ul> </ul>
</p> </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))))) (resume-url-servlet-name path-string)))))
(lookup-continuation-table (lookup-continuation-table
(lambda (instance continuation-table continuation-id) (lambda (instance continuation-table continuation-id)