I'm not muddling, but you just misinterpret. Why not jpeg itself? Application can output whatever it wants, right?
Again, here is part of template. Originally I made mistake, because I didn't remember syntax. Here how it should be
...
<img src="%item-name%/~thumbnail" />
...
[thumbnail]
{.add header|Content-Type: image/jpeg.}
{.exec|resize.exe "%current-path%".}
HFS will generate the following HTML
...
<img src="picture1.jpeg/~thumbnail" />
...
Now browser receives this HTML, it sees <img> tag and 'src'. Assuming, that addres of page is
http://mysite.com/somefolder/ the browser now tries to fetch URL "
http://mysite.com/somefolder/picture1.jpeg/~thumbnail" to load image.
If I remember correctly it will cause HFS to take section "thumbnail" from template, process it and the result return to browser.
Now, if I understand right, you say that {.exec.} will not cause HFS to replicate application's output to browser?
Lets consider another example. I have section in template
[mysection]
{.exec|print_some_html.exe.}
output of print_some_html.exe is always same:
<html>
<body>
Hello World!
</body>
</html>Now I type in browser this address
http://mysite.com/~mysectionWhat will I see in browser? Empty page? "Hello World"?