Re: [Erlyaws-list] obfuscated internal redirect to image file

[Steve V. <vi...@ie...>]

On 1/20/09, Buggaboo <bug...@gm...> wrote:
>  Hi y'all,
>
>  {page, "file.jpeg"} doesn't seem to find any files at all, but yaws is
> reacting nicely with "The requested URL meh.jpeg was not found on this
> server". I'm at a loss to where the relative path is located.

Well, I use {page, Path} in my own code so I know it works, and I just
tried it against 1.77 and it worked fine. But as you've already
surmised, yaws assumes the Path you're providing is absolute. If you
want to use {page, Path} for a path relative to the path of the
current request, you can create an absolute path for your file with
something like this:

{page, string:join([Arg#arg.prepath, "filename"], "/")}

where Arg is the name of the argument to your out/1 function and
"filename" is the relative name of the file whose contents you're
trying to send in your response. (Note that string:join/2 is a
relatively recent addition to Erlang/OTP so if you're using something
older than R12B-1 use filename:join/1 instead.)

--steve