URI-encode in the middleware?

[Cerchie]

I'm wondering why URI-encoding is left to the user?

I experimented a little this morning. In line 12 of headers.js, I inserted: request.headers.markdown = encodeURIComponent(request.headers.markdown);

Then, when I ran curl --location 'http://localhost:3000/blog/example' --header 'markdown: # Hello World' (I'll acknowledge it was difficult to get the original example markdown on one line, maybe that's part of it) I received a response including:

...
			
	<div class="blog">
		<h1 id="hello-world">Hello World</h1>

	</div>

so it seemed to be working from the curl response, but it was not reflected in the browser:

Curious about why this might be, but also, why the user must URI-encode as well.

[cassidoo]

Great question! Long story short, the URL encoding was added later because of how our image URLs are formed (and some special characters that were output into blogs). The weird characters overall didn't consistently display unless the URL encoding was added.