yssi ignored on appmods = </, myappmod> about yaws HOT 4 CLOSED

Need more info, I don't understand exactly what the problem is.

from yaws.

With my normal server configuration:
<server localhost>
port = 8080
listen = 0.0.0.0
deflate = true
docroot = /home/dev/hp
appmods = </, conductor>
</server>

Using the appmod file:
$ cat conductor.erl

-module(conductor).

-include("yaws_api.hrl").

-export([out/1]).

out(A) -> {yssi, "test.yaws"}.

And in the docroot folder I have:
$ cat test.yaws

<erl>
out(A) -> {html, "this is test.yaws in docroot"}.
</erl>

Calling the appmod gives me no results from the yssi:
$ curl http://127.0.0.1:8080/

$

However if I changes
appmods = </, conductor> to appmods = <myappmod, conductor>

And calls the appmod, the yssi works:
$ curl http://127.0.0.1:8080/myappmod

this is test.yaws in docroot
$

So in short returning {yssi, Filename} values from an appmod that uses / as the trigger does not work.

from yaws.

Thanks, good report now. I'll try to make time to have a look at this.

from yaws.

I had a look at this and this is not easy to fix, the return value {yssi, "test.yaws"}
will turn into appmod processing once again since there is an appmod at top.
The code was never written for this case to work.

I'd prefer to not fix this.

Sorry

from yaws.