opposite of internal-only?

[Alexandre Victoor <al...@fr.adp.com>]

Hello
I would like to know if it is possible to have a pipeline that can't be 
accessed internally.
I would like to be able to write something like that :

<map:match pattern="**" external-only="true">

I have already tried that :

<map:match pattern="**" internal-only="true">
...
</map:match>
<map:match pattern="**">
...
</map:match>

Unfortunately, the first one is always called despite the fact that it is 
only internal.
Is there already a sitemap feature that could help me ? I am using coconn 2.0.4
Regards

Alex


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org

Re: opposite of internal-only?

[Alexandre Victoor <al...@fr.adp.com>]

>You may be able to use a referer matcher/selector to try to guarantee that 
>the request is really coming from outside.  I fail to understand why you 
>need this.  Maybe elaborating on that would help come up with better options.
>
>Geoff

In my main pipeline I have something like that :

<map:match pattern="**">
          <map:act type="my action">
                 ...
                 ....
                 <map:generate src="cocoon:/{actionResult}"  type=... />
                 ...
         </map:act>
</map:match>

"cocoon:/{actionResult}" should be matched by another pipeline, but if not, 
I do not want cocoon to loop over and over...

Alex 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org

Re: opposite of internal-only?

[Geoff Howard <co...@leverageweb.com>]

Alexandre Victoor wrote:
> Hello
> I would like to know if it is possible to have a pipeline that can't be 
> accessed internally.

Don't think so - but why??  You trust external users from the internet 
more than your own code?

> I would like to be able to write something like that :
> 
> <map:match pattern="**" external-only="true">

Does not exist AFAIK.

> 
> I have already tried that :
> 
> <map:match pattern="**" internal-only="true">
> ...
> </map:match>
> <map:match pattern="**">
> ...
> </map:match>

This is incorrect unless I've really missed something.
internal-only belongs on the map:pipeline element. So,

<map:pipelines>
   <map:pipeline internal-only="true">
     <!-- all your internal map:matches go here -->
   </map:pipeline>
   <map:pipeline>
     <!-- all regular (internal/external) map:matches go here -->
   </map:pipeline>
</map:pipelines>
	
> Is there already a sitemap feature that could help me ? I am using 
> coconn 2.0.4

You may be able to use a referer matcher/selector to try to guarantee 
that the request is really coming from outside.  I fail to understand 
why you need this.  Maybe elaborating on that would help come up with 
better options.

Geoff


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org