Forum

Hiawatha version: Hiawatha v8.6, cache, IPv6, Monitor, reverse proxy, SSL, URL toolkit, XSLT
Copyright (C) by Hugo Leisink <hugo@leisink.net>
Operating System: Debian 7.0 "Wheezy"

Sorry for bringing this up again, but I'm still experiencing the issue I described on my -now closed- previous topic [www.hiawatha-webserver.org].

I've created three different bug reports with Valgrind. The first one, named "valgrind-first-setup.txt", is the result of the same configuration described on my previous post. Second one is named "valgrind-full-path-to-passwd.txt". It resulted after I've given the full path to my PasswordFile.

StartFile = index.html
ShowIndex = yes
PasswordFile = digest:/full/path/to/.passwd
LoginMessage = logs

Third one is named "valgrind-index-xslt.txt". It's been created after I changed the ShowIndex option.

StartFile = index.html
ShowIndex = /etc/hiawatha/index.xslt
PasswordFile = digest:/full/path/to/.passwd
LoginMessage = logs

Hope they help you to resolve the issue. Please let me know if I can be of any more help.

Regards,

Ali.

Did you change the content of /etc/hiawatha/index.xslt? If so, can you show it to me?

No, I have never touched it.

Can you try this version [www.leisink.net]. Please note that this is not an official release.

This is what I get from "hiawatha -v" now:

Hiawatha v8.7, cache, IPv6, Monitor, reverse proxy, SSL, URL toolkit, XSLT
Copyright (C) by Hugo Leisink <hugo@leisink.net>

These are the .hiawatha file configurations for the new valgrind bug reports:

valgrind-first-setup.txt

StartFile = index.html
ShowIndex = yes
PasswordFile = digest:.passwd
LoginMessage = logs

valgrind-full-path-to-passwd.txt

StartFile = index.html
ShowIndex = yes
PasswordFile = digest:/full/path/to/.passwd
LoginMessage = logs

valgrind-index-xslt.txt

StartFile = index.html
ShowIndex = /etc/hiawatha/index.xslt
PasswordFile = digest:.passwd
LoginMessage = logs

I saw the login screen only on the first one. However, after I entered the credentials stored in the .passwd, result was the same: server crashed in all cases.

I've sent the new bug reports to the same address, hope you find them useful.

Thanks for the support Hugo, last package fixed the issue.

After I compiled and installed the version you've sent, I was able to list the contents of the alias. Only thing I had to do was to modify the /logs rule in the WordPress URL toolkit for avoiding 404s:

UrlToolkit {
        ToolkitID = wordpress
        RequestURI exists Return
		Match ^/logs($|/$|/.*\.log$) Exit
        Match .* Rewrite /index.php
}