You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Justin Edelson (JIRA)" <ji...@apache.org> on 2010/09/10 19:26:33 UTC

[jira] Updated: (SLING-1750) All links/hrefs on initial content's index.html should be relative

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

Justin Edelson updated SLING-1750:
----------------------------------

        Summary: All links/hrefs on initial content's index.html should be relative  (was: initial content's index.html doesn't load sling.js when war is deployed as a sub context)
    Description: for example... if you deploy the sling war to a servlet container at a subcontext (i.e. /sling), the index.html page doesn't have the correct URL for sling.js  (was: if you deploy the sling war to a servlet container at a subcontext (i.e. /sling), the index.html page doesn't have the correct URL for sling.js)

> All links/hrefs on initial content's index.html should be relative
> ------------------------------------------------------------------
>
>                 Key: SLING-1750
>                 URL: https://issues.apache.org/jira/browse/SLING-1750
>             Project: Sling
>          Issue Type: Bug
>          Components: Launchpad
>            Reporter: Justin Edelson
>            Assignee: Justin Edelson
>             Fix For: Launchpad Content 2.0.6
>
>
> for example... if you deploy the sling war to a servlet container at a subcontext (i.e. /sling), the index.html page doesn't have the correct URL for sling.js

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