[ 
https://issues.apache.org/jira/browse/COUCHDB-348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13845657#comment-13845657
 ] 

Benjamin Young commented on COUCHDB-348:
----------------------------------------

Yeah, let's avoid the prefix conversation. If it must be done, it should happen 
and be discussed elsewhere...so we don't derail this antique bug getting fixed. 
;)

[~janl], I very much like the approach you've described. I do think it's 
feasible to at least detect the big 3 browsers (Firefox, WebKit collective, and 
IE) and route them accordingly--untold numbers of web servers do this 
successfully...certainly we can find a way.

Another orthogonal discussion would be the use of something like HAL 
(Hypermedia Application Language) for defining things like this link in the 
JSON we return...but that's a separate can of worms that should stay separate. 
;)

+1 on adding a link under vendor for now, and routing {{/}} to {{/_utils}} (or 
wherever based on a config setting...ideally) following that.

Thanks, [~janl]

> / should redirect to a human readable page when accessed from a browser
> -----------------------------------------------------------------------
>
>                 Key: COUCHDB-348
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-348
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: HTTP Interface
>            Reporter: Chris Anderson
>            Assignee: Robert Newson
>         Attachments: COUCHDB_348_01.patch, COUCHDB_348_02.patch, 
> COUCHDB_348_03.patch, encs.erl
>
>
> As more people are adopting CouchDB, the number of questions along the lines 
> of "All I see is {"couchdb":"Welcome","version":"0.10.0a773399"}, what now?"
> If this page redirected to /_utils/ (or maybe something more user-focussed) 
> when the accept headers included html, we could make the first-time user 
> experience more palatable.
> There's some code in COUCHDB-234 that might be helpful here.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Reply via email to