Ian Bicking <[EMAIL PROTECTED]>:
>
> On Thu, 2002-02-07 at 06:46, Magnus Lie Hetland wrote:
...
> > file ending? (Adding them to the endings-to-ignore list doesn't do any
> > good...)
>
> WebKit/Configs/Application.config: ExtensionsToIgnore
I'm not sure you read the sentence you replied to here
I still haven't been able to ssh in, but it certainly looked like the
appserver was down, as no servlet was responding. A friend restarted WK and
all is fine now, so...
Any pointers as to how I can make the connection more robust? Is it worth
re-using the connection, or should I re-initiali
There's a possibility that, because your website got a lot of hits some
resource was exhausted (memory, maybe), and that could cause multiple
problems. I.e., whatever closed the connection also caused WK to crash.
Alternatively, I imagine there's also a number of reasons why a MySQL
connection c
On Thu, 2002-02-07 at 06:46, Magnus Lie Hetland wrote:
> I've added password protection to a couple of pages, and since I use
> Cheetah (at the moment), there is a .tmpl file lying around. I find it
> practical (because of the cheetah-compile program) to have these in
> the published directory, bu
I've added password protection to a couple of pages, and since I use
Cheetah (at the moment), there is a .tmpl file lying around. I find it
practical (because of the cheetah-compile program) to have these in
the published directory, but I would not like WebKit to show them
(because that would be a
I am trying to diagnose a WebKit crash: my website got a large number of
hits yesterday, and apparently WK crashed completely. WK is connected to
MySQL on the backend, and the last thing I saw from WK (I cannt telnet to
the box to do forensics on WK yet) was a MySQL error: "lost connection to
