Some .gmi files are displayed as plain text on my page #223

New Issue

alexlehm · 2023-02-16T01:36:39Z

alexlehm commented

2023-02-16 01:36:39 +00:00

I have started a gemlog page on my site and for some reason Bombadillo is showing the post files as plain text while it displays all regular pages as gemini text. This happens with two different servers with the same content, I am not sure if that is a server error or a client error, it works with e.g. Lagrange or the Gemini web proxies but it does not work with Amfora either.

alexlehm commented

2023-02-16 01:38:48 +00:00

my page is at gemini://alexlehm.pollux.casa/

sloum commented

2023-02-16 02:13:47 +00:00

I have no problems loading the given address as text/gemini in the current version of bombadillo.

What version are you running? There are two ways to find out:

At your shell prompt enter: bombadillo -v
In bombadillo use the command :version

In general bombadillo will only render a gmi file as gemtext if the status code from the server indicates a mime type of text/gemini. If anything other than that is sent by the server, bombadillo will render the file as plain text (unless it is an image: png or jpg; in which case it will attempt to render the image in braille characters).

Let me know what you find :)

I have no problems loading the given address as `text/gemini` in the current version of bombadillo. What version are you running? There are two ways to find out: 1. At your shell prompt enter: `bombadillo -v` 2. In bombadillo use the command `:version` In general bombadillo will only render a gmi file as gemtext if the status code from the server indicates a mime type of `text/gemini`. If anything other than that is sent by the server, bombadillo will render the file as plain text (unless it is an image: png or jpg; in which case it will attempt to render the image in braille characters). Let me know what you find :)

alexlehm commented

2023-02-16 18:00:14 +00:00

I believe the server sends text/gemini (when I run a cli request, I get text/gemini lang=en)

I use Bombadillo version: 2.3.3 (in fact I run that on rawtext.club since I just joined the site)

I believe the server sends text/gemini (when I run a cli request, I get text/gemini lang=en) I use Bombadillo version: 2.3.3 (in fact I run that on rawtext.club since I just joined the site)

alexlehm commented

2023-02-16 18:01:03 +00:00

This url does not work for me:

gemini://alexlehm.pollux.casa:1965/gemlog/2023-Feb-12.gmi

This url does not work for me: gemini://alexlehm.pollux.casa:1965/gemlog/2023-Feb-12.gmi

alexlehm commented

2023-02-16 18:03:06 +00:00

I probably have messed something up with the files but I am not getting what

alexlehm commented

2023-02-16 18:07:30 +00:00

The mime type looks ok:

$ ./gemini-request.sh -h alexlehm.pollux.casa /gemlog/2023-Feb-12.gmi 2>/dev/null|head
20 text/gemini; lang=en
# Sun, 12 Feb 2023 23:43:40 +0000

<p>World Community Grid says in their newsletter that I have not returned a result for 8 years, that is probably because I decided that it uses too much CPU to run it,maybe I should start again</p>

# Sun, 12 Feb 2023 20:26:32 +0000

<p>I wonder how long I am using unix and I never get the access bits right (chmod 666 instead of chmod 777)</p>

# Sun, 12 Feb 2023 20:04:02 +0000

The mime type looks ok: ``` $ ./gemini-request.sh -h alexlehm.pollux.casa /gemlog/2023-Feb-12.gmi 2>/dev/null|head 20 text/gemini; lang=en # Sun, 12 Feb 2023 23:43:40 +0000 World Community Grid says in their newsletter that I have not returned a result for 8 years, that is probably because I decided that it uses too much CPU to run it,maybe I should start again # Sun, 12 Feb 2023 20:26:32 +0000 I wonder how long I am using unix and I never get the access bits right (chmod 666 instead of chmod 777) # Sun, 12 Feb 2023 20:04:02 +0000 ```

sloum commented

2023-02-16 20:04:50 +00:00

It is rendering fine as gemtext. But gemtext is not html. You have put a bunch of html into your gemtext. So if you are expecting  and <a href="...">...</a> tags to render... that wont happen in a gemtext document. You need to use the gemtext format. Here is an introduction to gemtext.

It is rendering fine as gemtext. But gemtext is not html. You have put a bunch of html into your gemtext. So if you are expecting `` and `<a href="...">...</a>` tags to render... that wont happen in a gemtext document. You need to use the gemtext format. Here is [an introduction to gemtext](https://gemini.circumlunar.space/docs/gemtext.gmi).

sloum commented

2023-02-16 20:08:55 +00:00

You are certainly welcome to serve html over the gemini protocol. But most clients wont render it as html and will just display it as text/plain. The reason some other browsers displayed your file the way you expected it is because they are using a web renderer for their gemini client. As such, they are converting gemtext to html and then rendering. Since you are already using html in your gemtext it just rendered... because they are not escaping html in the gemtext content. This is actually something that can potentially allow javascript injection attacks, to a certain degree. What clients displayed your links and p tags the way you expected them? I'm happy to reach out to those developers and let them know about the security vulnerability.

You are certainly welcome to serve html over the gemini protocol. But most clients wont render it as html and will just display it as `text/plain`. The reason some other browsers displayed your file the way you expected it is because they are using a web renderer for their gemini client. As such, they are converting gemtext to html and then rendering. Since you are already using html in your gemtext it just rendered... because they are not escaping html in the gemtext content. This is actually something that can potentially allow javascript injection attacks, to a certain degree. What clients displayed your links and p tags the way you expected them? I'm happy to reach out to those developers and let them know about the security vulnerability.

alexlehm commented

2023-02-16 20:15:45 +00:00

It is not rendering the sections with the dates either. the

tags come from my converter script, that is not a good example.

Currently in bombadillo it looks like this:

Lagrange does not render the p tags either, but it displays the date entries

It is not rendering the sections with the dates either. the tags come from my converter script, that is not a good example. Currently in bombadillo it looks like this: ![image](/attachments/2691d0eb-3664-463a-b5c3-f5e9f40d4a2a) Lagrange does not render the p tags either, but it displays the date entries ![image](/attachments/c3ed7153-36c2-4b6e-902b-f106e4d7c625)

image.png

51 KiB

image.png

150 KiB

alexlehm commented

2023-02-16 20:20:35 +00:00

I think I found what my thinking error is, the tty client does not render headings and displays # headling instead while the graphical client uses a larger font. Then it is completely correct and I just have to clean up the HTML to convert it to gemtext properly

sloum commented

2023-02-16 20:28:17 +00:00

Ah. yes! Bombadillo just displays the heading level (I think it may bold a top level heading, but I cannot remember) withe # char since the tty cannot display in variable font sizes.

Good to hear that Lagrange is not rendering the P tags either.

Ah. yes! Bombadillo just displays the heading level (I think it may bold a top level heading, but I cannot remember) withe `#` char since the tty cannot display in variable font sizes. Good to hear that Lagrange is not rendering the P tags either.

alexlehm commented

2023-02-16 20:45:05 +00:00

I am working on converting the html tags to gemtext now

alexlehm closed this issue

2023-02-16 20:45:10 +00:00

Sign in to join this conversation.