GET request for '/' should return HTTP 200

[gbalint]

GET request for just '/' (as opposed to bzz:/ etc.) should return a HTTP 200 and some minimal status info, not an error about an invalid protocol

https://github.com/ethereum/go-ethereum/blob/master/swarm/api/http/server.go#L555

[cobordism]

Ideally this page would also explain how to add a bzz:// URL handler to your browser (if there isn't one yet)

[gbalint]

Note: you can not add a bzz:// handler to your browser, see #151 (comment)

[cooganb]

@gbalint just FYI, i'm poking around here to see if i can help on this issue.

[cooganb]

@gbalint what kind of status info do you think would be good? and would that be delivered as an error message?

just for reference, here's what i'm getting when i ping localhost:8500/ :

[cobordism]

Here is an idea.
The page starts with

Welcome to Ethereum Swarm.

and then have an input form with title "enter a name or a hash" and default value theswarm.eth and when the button is clicked, the user gets redirected to bzz://theswarm.eth

Than, in future, we can extend this landing page with links to the stats page, admin page etc. etc.

[holisticode]

I agree it should be a landing page for swarm. And can serve as 'status' until a more detailed definition of what 'status' should return. Should maybe check for accept header, also json requests should be accepted (returning just 200 OK).

…

On 24 Dec 2017 12:27 p.m., "Aron" ***@***.***> wrote: Here is an idea. The page starts with Welcome to Ethereum Swarm. and then have an input form with title "enter a name or a hash" and default value theswarm.eth and when the button is clicked, the user gets redirected to bzz://theswarm.eth Than, in future, we can extend this landing page with links to the stats page, admin page etc. etc. — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#155 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAFY34h-BX7NXmMZ6ibwM1Uye7-hNuNAks5tDomBgaJpZM4Q-_Nr> .

[cooganb]

Great, so we're thinking about making it a landing page with an input form that can accept hashes or ENS domains, knit together the correct address and send the user on their way?

Any other links to be provided on the landing page?

@holisticode how (if at all) does the page currently handle json requests? And what's the protocol now for accept header?

Last, are there any web development guidelines for swarm that could direct what the landing page looks like?

Thanks in advance for any help!

[cobordism]

I feel like having a minimally functional landing page is a good first step.
Once it is up and running, we can talk about tweaking it and adding features.

The current landing-error-page I consider to be (almost) a bug.

Great, so we're thinking about making it a landing page with an input form that can accept hashes or ENS domains, knit together the correct address and send the user on their way?

that's my feeling for a good minimal working example, yes.

Any other links to be provided on the landing page?

Perhaps just one to https://swarm-guide.readthedocs.io/en/latest/ ?

[cooganb]

@homotopycolimit okay, sounds good.

i'd like to get some work done on this. i want to make sure my git etiquette is correct: i'll create a new branch from the ethereum-go master and work on a new method for the HandleGetFile function where entering in an "empty" address, like / or bzz:// would result in the user getting a very basic landing page which would have a header, an input form & button for hashes / ENS and link to swarm docs?