You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Nuwan Dias (JIRA)" <ji...@apache.org> on 2013/01/15 03:58:12 UTC

[jira] [Updated] (SYNAPSE-919) REST_URL_POSTFIX ignored when accessing API with the OPTIONS method

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

Nuwan Dias updated SYNAPSE-919:
-------------------------------

    Description: 
Consider the following API configuration.

<api xmlns="http://ws.apache.org/ns/synapse" name="TwitterAPI" context="/twitter" version="1.0.0" version-type="url">
    <resource methods="POST GET OPTIONS DELETE PUT" url-mapping="/*">
        <inSequence>
            <send>
                  <endpoint name="Twitter_EP">
                            <address uri="http://twitter.com/search"/>
                  </endpoint>
            </send>
        </inSequence>
        <outSequence>
            <send/>
        </outSequence>
    </resource>
</api>

When this API is accessed as http://localhost:8280/twitter/1.0.0/a/b/c, the a/b/c string should be considered as the REST_URL_POSTFIX and appended to the endpoint url as its suffix. However, this currently does not happen if the OPTIONS http method is used for invoking the API and the url suffix is ignored. 

  was:
Consider the following API configuration.

<api xmlns="http://ws.apache.org/ns/synapse" name="TwitterAPI" context="/twitter" version="1.0.0" version-type="url">
    <resource methods="POST GET OPTIONS DELETE PUT" url-mapping="/*">
        <inSequence>
            <send>
                  <endpoint name="Twitter_EP">
                            <address uri="http://twitter.com/search"/>
                  </endpoint>
            </send>
        </inSequence>
        <outSequence>
            <send/>
        </outSequence>
    </resource>
</api>

When this API is accessed as http://localhost:8280/twitter/1.0.0/a/b/c, the a/b/c string should be considered as the REST_URL_POSTFIX and appended to the endpoint url as its suffix. However, this currently does not happen and the url suffix is ignored. 

    
> REST_URL_POSTFIX ignored when accessing API with the OPTIONS method
> -------------------------------------------------------------------
>
>                 Key: SYNAPSE-919
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-919
>             Project: Synapse
>          Issue Type: Bug
>            Reporter: Nuwan Dias
>
> Consider the following API configuration.
> <api xmlns="http://ws.apache.org/ns/synapse" name="TwitterAPI" context="/twitter" version="1.0.0" version-type="url">
>     <resource methods="POST GET OPTIONS DELETE PUT" url-mapping="/*">
>         <inSequence>
>             <send>
>                   <endpoint name="Twitter_EP">
>                             <address uri="http://twitter.com/search"/>
>                   </endpoint>
>             </send>
>         </inSequence>
>         <outSequence>
>             <send/>
>         </outSequence>
>     </resource>
> </api>
> When this API is accessed as http://localhost:8280/twitter/1.0.0/a/b/c, the a/b/c string should be considered as the REST_URL_POSTFIX and appended to the endpoint url as its suffix. However, this currently does not happen if the OPTIONS http method is used for invoking the API and the url suffix is ignored. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org