Martin Baehr wrote (previous subject was: [WWWOFFLE-Users] Alternative WWWOFFLE implementation):
> is this a good time to open a wishlist discussion? > > there are a few things i have been wondering about or would like to see: > > remove > ssl-allow-port = (integer) > https should be allowed on any port, just like http. > many servers i work with use alternative ports for webserver configuration, > it is a pain having to add each port into the config manually. I don't see a need to change this feature myself. > don't delete old files if a refresh returns a 404. > sometimes i want to archive pages, and it hurts to loose them, > because they are not anymore available on the site. > (better, i want to archive them because they are not on the site anymore) Interesting idea. The wwwoffle server always makes a backup copy of an existing spool file before writing a new one. So it should not be too difficult to make wwwoffle restore the backup file if the response code was 404. I think it is best to make this a configurable option, and not standard behaviour. There is the question though what to send to the browser while wwwoffle is online. Should the page containing the 404 response code be sent or the contents of the old spool file? In the first case you will only be able to see the content you're interested in while wwwoffle is offline. In the second case you'll be looking at stale content without necessarily realizing it. I'll think about it some more and maybe I'll try to implement it. -- Paul A. Rombouts <[EMAIL PROTECTED]> My alternative WWWOFFLE implementation page: http://www.phys.uu.nl/~rombouts/wwwoffle.html
