Inconsistent file handler across browsers

[dctucker]

In my application I want to serve an image to the UI, so I create a file handler. When opening the window using Firefox, the UI displays the expected image via CSS background-image or HTML <img/> tag. However, when I use wbWebview, no image is displayed, and the HTML tag shows the "unknown image" question-mark icon.

If I instead specify a rootPath and comment out the file handler, the UI will display the image. I don't want to do that though, because it gives me much less control over what the UI can access in my filesystem, and it precludes being able to bundle assets as part of my binary executable.

I don't know the best way to investigate why this is happening but I'd be happy to provide more information given a bit of debugging tips.

[dctucker]

More information: This appears to fail due to Webview being less graceful at handling arbitrary content types than Firefox. Returning a full HTTP response with headers including content type and length makes this work as expected. It would be helpful if the Nim examples could be updated to match the C example so that this is clearer to the developer. Even better if MIME-type detection could be done automatically OR explicitly specified via a helper function to format a response.

[AlbertShown]

Yes, the new file handler should return the full HTTP header + body.
Unfortunately, Nim is not being updated for a while now... hope someone has free time to update bindings soon... I may do it later this week.