Cannot acces the image file directly

[ikkefc3]

Hi,
I have a question. I can acces the image by typing in http://:5000/ in my browser and it works.
It shows a blank page on my E-ink display, for which I think I would need to point it to the image file directly.
Is this somehow possible?
The format would then be:
http://:5000/image.png or something.

If this is possible, it would be very nice because then this project is compatible with a lot more e-ink solutions then only the Kindle screensaver.

[ikkefc3]

Never mind. Found a fork that does this.

[sibbl]

I'd be interested into getting more details about this request.

When accessing http://:5000/, the image file is directly returned.

Is it about a requirement of any e-ink devices to have the file name and file extension in the URL?

[ikkefc3]

Thank you for your answer! Yes it’s indeed about a requirement to have the file name and extension in the name directly. I have an Inkplate 6plus and just inputting the link yields a blank image on screen, but pointing to a png or jpg does het the right image on screen. Op ma 26 aug 2024 om 11:36 schreef Sebastian Schubotz < ***@***.***>

…

I'd be interested into getting more details about this request. When accessing http://:5000/, the image file is directly returned. Is it about a requirement of any e-ink devices to have the file name and file extension in the URL? — Reply to this email directly, view it on GitHub <#129 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXDEMKSSQS4KDKC53PU2BPDZTLZJLAVCNFSM6AAAAABNC3TTAKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBZG44DAMZQGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[ikkefc3]

I found a very simple workaround. Just add ?.png to the url. Example:
http://:5000/?.png

This will save some people for running a whole extra docker instance just to get the png.