You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2008/02/11 09:16:08 UTC

[jira] Created: (SLING-243) Handle GET requests by method name not just by request extension

Handle GET requests by method name not just by request extension
----------------------------------------------------------------

                 Key: SLING-243
                 URL: https://issues.apache.org/jira/browse/SLING-243
             Project: Sling
          Issue Type: Improvement
          Components: ServletResolver
            Reporter: Felix Meschberger
             Fix For: 2.0.0


Currently the name of the script to call to handle a request is based on the request extension for GET and HEAD requests and on the request method for all other requests. This works fairly well for scripts handling single extensions. But it does not scale well for servlets (and scripts BTW), which are able to handle more than just a single extension, such as the launchpad default servlet.

Therefore - just for GET/HEAD  requests - the script name should just be looked up by request extension and if no script can be found by the request method name just like for all other methods.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (SLING-243) Handle GET requests by method name not just by request extension

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger closed SLING-243.
-----------------------------------

    Resolution: Fixed

Fixed in Rev. 620447 and added a simple test case in Rev. 627732.

I close this now fixed.

> Handle GET requests by method name not just by request extension
> ----------------------------------------------------------------
>
>                 Key: SLING-243
>                 URL: https://issues.apache.org/jira/browse/SLING-243
>             Project: Sling
>          Issue Type: Improvement
>          Components: ServletResolver
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: 2.0.0
>
>
> Currently the name of the script to call to handle a request is based on the request extension for GET and HEAD requests and on the request method for all other requests. This works fairly well for scripts handling single extensions. But it does not scale well for servlets (and scripts BTW), which are able to handle more than just a single extension, such as the launchpad default servlet.
> Therefore - just for GET/HEAD  requests - the script name should just be looked up by request extension and if no script can be found by the request method name just like for all other methods.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (SLING-243) Handle GET requests by method name not just by request extension

Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SLING-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567544#action_12567544 ] 

Bertrand Delacretaz commented on SLING-243:
-------------------------------------------

Agreed, I think we had this in microsling: fallback to get.esp if html.esp is not found, for example.

> Handle GET requests by method name not just by request extension
> ----------------------------------------------------------------
>
>                 Key: SLING-243
>                 URL: https://issues.apache.org/jira/browse/SLING-243
>             Project: Sling
>          Issue Type: Improvement
>          Components: ServletResolver
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: 2.0.0
>
>
> Currently the name of the script to call to handle a request is based on the request extension for GET and HEAD requests and on the request method for all other requests. This works fairly well for scripts handling single extensions. But it does not scale well for servlets (and scripts BTW), which are able to handle more than just a single extension, such as the launchpad default servlet.
> Therefore - just for GET/HEAD  requests - the script name should just be looked up by request extension and if no script can be found by the request method name just like for all other methods.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (SLING-243) Handle GET requests by method name not just by request extension

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger reassigned SLING-243:
---------------------------------------

    Assignee: Felix Meschberger

> Handle GET requests by method name not just by request extension
> ----------------------------------------------------------------
>
>                 Key: SLING-243
>                 URL: https://issues.apache.org/jira/browse/SLING-243
>             Project: Sling
>          Issue Type: Improvement
>          Components: ServletResolver
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: 2.0.0
>
>
> Currently the name of the script to call to handle a request is based on the request extension for GET and HEAD requests and on the request method for all other requests. This works fairly well for scripts handling single extensions. But it does not scale well for servlets (and scripts BTW), which are able to handle more than just a single extension, such as the launchpad default servlet.
> Therefore - just for GET/HEAD  requests - the script name should just be looked up by request extension and if no script can be found by the request method name just like for all other methods.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.