You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2007/11/20 14:30:43 UTC
[jira] Created: (SLING-107) Use request extension instead of
Content-Type to build script name
Use request extension instead of Content-Type to build script name
------------------------------------------------------------------
Key: SLING-107
URL: https://issues.apache.org/jira/browse/SLING-107
Project: Sling
Issue Type: Improvement
Components: microsling
Reporter: Bertrand Delacretaz
Priority: Minor
We seem to agree on the list ("microsling: extension vs. mime-type script resolution") that using the request extension to resolve scripts is simpler and less risky than using the Content-Type as microsling does now.
Unless someone objects, I think we can go ahead and implement this change.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-107) Use request extension instead of
Content-Type to build script name
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543889 ]
Felix Meschberger commented on SLING-107:
-----------------------------------------
In addition, I suggest using "GET" as the fall back name in case the request has no extension.
> Use request extension instead of Content-Type to build script name
> ------------------------------------------------------------------
>
> Key: SLING-107
> URL: https://issues.apache.org/jira/browse/SLING-107
> Project: Sling
> Issue Type: Improvement
> Components: microsling
> Reporter: Bertrand Delacretaz
> Priority: Minor
>
> We seem to agree on the list ("microsling: extension vs. mime-type script resolution") that using the request extension to resolve scripts is simpler and less risky than using the Content-Type as microsling does now.
> Unless someone objects, I think we can go ahead and implement this change.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-107) Use request extension instead of
Content-Type to build script name
Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bertrand Delacretaz resolved SLING-107.
---------------------------------------
Resolution: Fixed
Implemented in revision 599511, see SlingResourceTypeRenderingTest, NodetypeRenderingTest and ScriptFilenameBuilderTest for details.
> Use request extension instead of Content-Type to build script name
> ------------------------------------------------------------------
>
> Key: SLING-107
> URL: https://issues.apache.org/jira/browse/SLING-107
> Project: Sling
> Issue Type: Improvement
> Components: microsling
> Reporter: Bertrand Delacretaz
> Priority: Minor
>
> We seem to agree on the list ("microsling: extension vs. mime-type script resolution") that using the request extension to resolve scripts is simpler and less risky than using the Content-Type as microsling does now.
> Unless someone objects, I think we can go ahead and implement this change.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.