Comment

Comment by natch

Edit: my bad, I literally clicked on an example link provided in the page, which clearly shows the same URL format I used in my post, and edited the URL to have the strings for the Luke passage. I see that's the wrong syntax. Safari must be doing something funny… nope, that wasn't it. It was me, not noticing that %20 was an encoded + since it was mashed together with another number which threw me off.

Earlier question was asking why a controversial passage was not found.

Corrected URL: http://bible-api.com/luke+14:26

parent natch 6 years ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton