couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-2353) Normalize special CouchDB headers name
Date Sat, 08 Nov 2014 14:59:33 GMT


ASF GitHub Bot commented on COUCHDB-2353:

GitHub user kxepal opened a pull request:

    Normalize special CouchDB headers names


You can merge this pull request into a Git repository by running:

    $ git pull 2353-normalize-special-headers-names

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #15
commit 72e6f34e26cb9ebc6add9feccfe2b9e2226c417e
Author: Alexander Shorin <>
Date:   2014-11-08T14:50:44Z

    Normalize special CouchDB headers names


> Normalize special CouchDB headers name
> --------------------------------------
>                 Key: COUCHDB-2353
>                 URL:
>             Project: CouchDB
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: Database Core
>            Reporter: Alexander Shorin
> So far we have:
> - X-Couch-Id
> - X-Couch-Update-NewRev
> - X-Couch-Full-Commit
> - X-CouchDB-VHost-Path
> - X-CouchDB-WWW-Authenticate
> - X-CouchDB-Requested-Path
> - X-Couch-Request-ID
> - X-Couch-Stack-Hash
> - X-CouchDB-Body-Time
> - X-Couch-Test-Auth
> - X-Auth-CouchDB-Username
> - X-Auth-CouchDB-Roles
> - X-Auth-CouchDB-Token
> First, I'd like to see them sharing common prefix: X-Couch or X-CouchDB, not both. For
consistency. Personally, I think X-CouchDB is better name since it completely matches with
the project name.
> Second, some name cleanup would be nice: it doesn't oblivious what X-Couch-Id belongs
to while there is X-Couch-Request-Id and X-Couch-Update-NewRev is too verbose: X-Couch-Doc-Id
and X-Couch-Doc-Rev would be more clean IMHO. Or X-CouchDB-*.
> Third is an idea to drop X- prefix as per [RFC-6648|].
Personally, I don't like this RFC as like as idea of pollution standard headers name space
with custom ones, but what do you think about? Is it worth to keep or drop X- prefix?

This message was sent by Atlassian JIRA

View raw message