[ 
https://issues.apache.org/jira/browse/DTACLOUD-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ramesh A closed DTACLOUD-34.
----------------------------

    
> Driver selection does not work when using WEBrick server
> --------------------------------------------------------
>
>                 Key: DTACLOUD-34
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-34
>             Project: DeltaCloud
>          Issue Type: Bug
>          Components: Server
>         Environment: Fedora 14, deltacloud git-svn-id: 
> https://svn.apache.org/repos/asf/incubator/deltacloud/trunk@1097646 
> 13f79535-47bb-0310-9956-ffa450edef68
>            Reporter: Chris Lalancette
>            Assignee: Michal Fojtik
>         Attachments: deltacloudd-webrick-driverswitch.patch
>
>
> One of the new features of deltacloud 0.3.0 is the ability to switch backend 
> drivers on a per-request basis.  One of the ways to do this is to create a 
> URL like: http://localhost:3001/api;driver=mock.  When using the thin 
> webserver, this invocation works just fine, and you get the output from the 
> mock driver.  However, when using the WEBrick server, this does not work and 
> you get an error page that says "Sinatra doesn't know this ditty" (this 
> generally means a 404).  The relevant part of the deltacloudd log looks like:
> 127.0.0.1 - - [29/Apr/2011 09:04:03] "GET 
> http://localhost:3001/api?api[driver]=mock HTTP/1.1" 404 433 0.0124
> That GET request is actually wrong; it should be something like "GET 
> /api?api[driver]=mock", not the full URL.  This observation led me to a patch 
> (which I will attach), which seems to improve the situation.  However, it 
> doesn't completely solve the problem, as even with this patch applied I still 
> cannot make driver selection work.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to