couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benoit Chesneau (Commented) (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1416) the requested_path that is passed to a show is wrong on a vhost with a path
Date Thu, 23 Feb 2012 08:13:48 GMT


Benoit Chesneau commented on COUCHDB-1416:

It is isn't possible to use the test suite to tests vhists. Since the vhost is depending on
the Host header. It's unlikely that you can change it in your ajax request. 

I'm surprised you can't get this path since we are using it for the oauth check. Can't you
use the header `x-couchdb-vhost-path` ? 

Anyway, the full problem right now, is that we don't pass any record while rewriting the uri.
 I can see 2 solutions in near future:

1. Keeping a state and sendint oit back when the mochiweb request have been modified
2. Keeping this state in the registry which was already proposed when we have to manage this

 I will have a look on it this week.

> the requested_path that is passed to a show is wrong on a vhost with a path 
> ----------------------------------------------------------------------------
>                 Key: COUCHDB-1416
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>          Components: HTTP Interface
>    Affects Versions: 1.2
>            Reporter: Ryan Ramage
>            Priority: Minor
> In a show or list, it is impossible to construct a full url that an end user could use
to re-request the resource, given the various combinations of vhosts and rewrites. 
> The major one is if the vhost contains a path component, this path information is not
passed to the show at all. 
> I have created three tests that highlight the condition, currently failing for one test,
with the two passing to prevent regressions.
> The commit can be found here:
> I have talked this over with JasonSmith and bennoitc on #couchdb and they asked me to
write the tests and raise the jira. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message