Hi,
Roy T. Fielding schrieb:
On Nov 24, 2008, at 5:06 AM, Felix Meschberger wrote:
Better yet, we might do regular expression matching and referencing:
/etc/map/http/www.(.)*.com.80/
+-- sling:contentPrefix = /content/sites/$1/
Question, though, is how
Hi,
Roy T. Fielding schrieb:
On Nov 23, 2008, at 1:42 PM, Felix Meschberger wrote:
Roy T. Fielding schrieb:
I think that Sling should use a content tree to establish the
root mappings; e.g.,
/etc/map/{scheme}/{host.port}/{uri_path}
with the default contents being
On Nov 23, 2008, at 1:42 PM, Felix Meschberger wrote:
Roy T. Fielding schrieb:
I think that Sling should use a content tree to establish the
root mappings; e.g.,
/etc/map/{scheme}/{host.port}/{uri_path}
with the default contents being
/etc/map/http/example.com.80/
+--
On Nov 24, 2008, at 5:06 AM, Felix Meschberger wrote:
Better yet, we might do regular expression matching and referencing:
/etc/map/http/www.(.)*.com.80/
+-- sling:contentPrefix = /content/sites/$1/
Question, though, is how to get these strings into the
[
https://issues.apache.org/jira/browse/SLING-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12650789#action_12650789
]
Felix Meschberger commented on SLING-249:
-
In Rev. 720647 I implemented a first shot
[
https://issues.apache.org/jira/browse/SLING-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12650808#action_12650808
]
Felix Meschberger commented on SLING-249:
-
And here comes the new API of the
* absolute uri: starts with scheme://
Is the value of scheme important, or is it just to signal that this is
an absolute uri?
If the value is to be used in the resolution, then we should take into
account that requests can be both http:// and https://
On Sun, Nov 23, 2008 at 7:30 PM, Felix
Hi,
Vidar Ramdal schrieb:
* absolute uri: starts with scheme://
Is the value of scheme important, or is it just to signal that this is
an absolute uri?
If the value is to be used in the resolution, then we should take into
account that requests can be both http:// and https://
On Sun,
Hi,
On Sat, Nov 22, 2008 at 1:11 AM, Roy T. Fielding [EMAIL PROTECTED] wrote:
...I think that Sling should use a content tree to establish the
root mappings; e.g.,
/etc/map/{scheme}/{host.port}/{uri_path}...
Agreed, much better to have this info in one place.
Some comments below on the
Hi,
On Sun, Nov 23, 2008 at 10:42 PM, Felix Meschberger [EMAIL PROTECTED] wrote:
...I think the mappings in the actual content would then just be real
aliases. For example:
/etc/map/http/localhost.*/
+-- sling:internalRedirect = /content/
/content/sample
Hi,
Bertrand Delacretaz schrieb:
Hi,
On Sat, Nov 22, 2008 at 1:11 AM, Roy T. Fielding [EMAIL PROTECTED] wrote:
...I think that Sling should use a content tree to establish the
root mappings; e.g.,
/etc/map/{scheme}/{host.port}/{uri_path}...
Agreed, much better to have this info in
Hi Vidar,
Vidar Ramdal schrieb:
Vidar Ramdal schrieb:
I'm not thrilled about the idea of dropping the cache on every change.
On Fri, Nov 21, 2008 at 12:47 PM, Felix Meschberger [EMAIL PROTECTED] wrote:
[...] This cache is of course not flushed on each modification in the
repository.
Hi,
Roy T. Fielding schrieb:
Sounds like an easy way to bypass delegated security.
Right, good point.
I don't like the idea of sprinkling root-level aliases
all over the content tree. I think it would be incredibly
complex and impossible to maintain over time, and not even
remotely
hi roy,
thanks for the thoughtful comment.
as a matter of fact felix and i actually discussed something along those
lines as a cachebut i really like the idea to have all the root mapping stored
somewhere centrally. we thought of putting it into /var, but i agree that
/etc/map may just be a good
Hi Felix!
On Fri, Nov 21, 2008 at 8:16 AM, Felix Meschberger [EMAIL PROTECTED] wrote:
As a consequence the existing mechanisms would be dropped:
VanityURLs : just set the URL on the target
URLMappings: just set the absolute path on the target root
Regexps: just set the respective
On Fri, Nov 21, 2008 at 8:16 AM, Felix Meschberger [EMAIL PROTECTED] wrote:
[...]
The sling:vanityPath property is multi-valued and contains URLs. These
URLs may be absolute or relative. An absolute URI includes the scheme,
authority and path. A relative omits the scheme and or authority part.
On Fri, Nov 21, 2008 at 10:03 AM, Vidar Ramdal [EMAIL PROTECTED] wrote:
This _is_ expensive and therefore absolutely requires caching.
Therefore, we will introduce a small (something like 1000 entries or
so), which may be used to directly map incoming requests to resources.
The cache is
[
https://issues.apache.org/jira/browse/SLING-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12649642#action_12649642
]
Bertrand Delacretaz commented on SLING-249:
---
We will probably not use query,
Hi,
Alexander Klimetschek schrieb:
BTW, how do I set vanity URLs in the current Sling? Do they allow
sub-paths when compared to vanity paths, eg. if there is a
sling:vanityPath = /foo set on /content/site/foo, will the request
/foo/something be forwarded to /content/site/foo/something with
On Fri, Nov 21, 2008 at 12:34 PM, Felix Meschberger [EMAIL PROTECTED] wrote:
You set an absolute path in the property. If the request URL cannot be
resolved, a query is run which asks for a sling:vanityPath property set
to the request URL path (actually HttpServletRequest.getPathInfo()). If
Hi Vidar,
Vidar Ramdal schrieb:
On Fri, Nov 21, 2008 at 8:16 AM, Felix Meschberger [EMAIL PROTECTED] wrote:
[...]
The sling:vanityPath property is multi-valued and contains URLs. These
URLs may be absolute or relative. An absolute URI includes the scheme,
authority and path. A relative omits
Hi Alex,
Alexander Klimetschek schrieb:
On Fri, Nov 21, 2008 at 12:34 PM, Felix Meschberger [EMAIL PROTECTED] wrote:
You set an absolute path in the property. If the request URL cannot be
resolved, a query is run which asks for a sling:vanityPath property set
to the request URL path (actually
[
https://issues.apache.org/jira/browse/SLING-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12649645#action_12649645
]
Felix Meschberger commented on SLING-249:
-
//element(*,
On Fri, Nov 21, 2008 at 12:47 PM, Felix Meschberger [EMAIL PROTECTED] wrote:
There are two caches actually:
One cache manages the values of sling:vanityPath properties, which may
be used as the domain root or root path. This cache is of course not
flushed on each modification in the
Vidar Ramdal schrieb:
I'm not thrilled about the idea of dropping the cache on every change.
On Fri, Nov 21, 2008 at 12:47 PM, Felix Meschberger [EMAIL PROTECTED] wrote:
[...] This cache is of course not flushed on each modification in the
repository.
Ah, sorry, I misunderstood.
In that
On Fri, Nov 21, 2008 at 4:22 PM, Vidar Ramdal [EMAIL PROTECTED] wrote:
Is the value of scheme important, or is it just to signal that this is
an absolute uri?
If the value is to be used in the resolution, then we should take into
account that requests can be both http:// and https://
Sounds like an easy way to bypass delegated security.
I don't like the idea of sprinkling root-level aliases
all over the content tree. I think it would be incredibly
complex and impossible to maintain over time, and not even
remotely scalable for virtual hosting setups.
I think that Sling
[
https://issues.apache.org/jira/browse/SLING-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12649333#action_12649333
]
Felix Meschberger commented on SLING-249:
-
I am now taking this issue up after it
[
https://issues.apache.org/jira/browse/SLING-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12649337#action_12649337
]
Vidar S. Ramdal commented on SLING-249:
---
Great that you're taking this task :)
What
[
https://issues.apache.org/jira/browse/SLING-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12649346#action_12649346
]
Felix Meschberger commented on SLING-249:
-
Good point. How about this: First look
[
https://issues.apache.org/jira/browse/SLING-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12649350#action_12649350
]
Vidar S. Ramdal commented on SLING-249:
---
That will work.
Another thing: At some
[
https://issues.apache.org/jira/browse/SLING-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12649366#action_12649366
]
Bertrand Delacretaz commented on SLING-249:
---
how about introducing a nodetype
[
https://issues.apache.org/jira/browse/SLING-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12649389#action_12649389
]
Alexander Klimetschek commented on SLING-249:
-
how about introducing a nodetype
[
https://issues.apache.org/jira/browse/SLING-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12649415#action_12649415
]
Vidar S. Ramdal commented on SLING-249:
---
@Felix
I hadn't thought of reverse mapping,
[
https://issues.apache.org/jira/browse/SLING-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12649425#action_12649425
]
Bertrand Delacretaz commented on SLING-249:
---
I'm not sure about caching
[
https://issues.apache.org/jira/browse/SLING-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12649420#action_12649420
]
Vidar S. Ramdal commented on SLING-249:
---
@Bertrand
I'm not sure about caching
Hi all,
I am now taking this to the list for discussion, because it gets very
interesting ;-)
We have just been discussion a slightly different approach, which may
even replace existing configuration setup of the JcrResourceResolver !
For now, we have the following:
Vanity URLs : replace
[
https://issues.apache.org/jira/browse/SLING-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12649619#action_12649619
]
Felix Meschberger commented on SLING-249:
-
Caching and cleanup:
Yes, we need a cache
[
https://issues.apache.org/jira/browse/SLING-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12582217#action_12582217
]
Vidar S. Ramdal commented on SLING-249:
---
What are the odds for this making the 1.0
[
https://issues.apache.org/jira/browse/SLING-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12582220#action_12582220
]
Bertrand Delacretaz commented on SLING-249:
---
I'm not planning to work on this, but
[
https://issues.apache.org/jira/browse/SLING-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12569798#action_12569798
]
Vidar S. Ramdal commented on SLING-249:
---
I suppose mod_proxy would let me do this, but
[
https://issues.apache.org/jira/browse/SLING-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12569799#action_12569799
]
Vidar S. Ramdal commented on SLING-249:
---
@Tobias Bocanegra:
Yes, such a mapping looks
[
https://issues.apache.org/jira/browse/SLING-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12570041#action_12570041
]
eric marts commented on SLING-249:
--
This is should be part of the request processing logic
Hi Bertrand,
This is in fact a viable solution - provided you have a an Apache server
to put in front - it is just another target you will have to manage..
Regards
Felix
Am Freitag, den 15.02.2008, 14:24 -0800 schrieb Bertrand Delacretaz
(JIRA):
[
44 matches
Mail list logo
