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

Taran Romana commented on COUCHDB-3206:
---------------------------------------

[~robertkowalski] Hi sorry for being late i had a look and its seems the dbs 
are listed and i can access the dbs but when i try to access a view in that db 
it will not encode the url for the view

e.g 
http://localhost:28000/#/database/account/90/1e/b7d40fa022cce3d3e2f5d27c2ec3/_design/lists/_view/listing

should be 
http://localhost:28000/#database/account%2F90%2F1e%2Fb7d40fa022cce3d3e2f5d27c2ec3/_design/lists/_view/listing
 instead

i will do an indept test and will report back if i find any other issue 

Thank you for your help

> Invalid conversion of / symbol
> ------------------------------
>
>                 Key: COUCHDB-3206
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-3206
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Fauxton
>            Reporter: Taran Romana
>
> when accessing any database with its name containing / 
> e.g. 
> 76/15/9720
> The ui tries to load the database using url 
> http://localhost:5984/76%252F15%252F9720
> but couchdb's api works with %2F and not with %252F
> due to this reason most of the requests to the database does not work, 
> e.g. adding new document, accesing attachments, viewing documents for a 
> specific view and most of the database features
> The fix for the issue is to use %2F instead of / or %252F and using the same 
> for fauxton url e.g 
> http://localhost:5984/_utils/#/database/76%2F15%2F9720/new_view
> works but the standard
> http://localhost:5984/_utils/#/database/76/15/9720/new_view 
> does not work and all other urls using the database name inside the url with 
> / instead of %2F causes errors.
> Edit: 
> i just noticed for some db's it uses %2F to access initial information about 
> the database and it works bu for majority %252F or / is used



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to