what is the amount of time the request connection will be alive for the first 
try?
what is the mechanism used to uniquely identify the browser client maybe From?
http://www.apl.jhu.edu/~hall/java/Servlet-Tutorial/Servlet-Tutorial-Request-Headers.html

In any case if the HTTP_FROM is the same as previous requests AND this is the 
second request what is amount of time the connection will be alive for second 
try

why not set a timer on second access which notifies you after 
USER_CONFIGURABLE_TIMEFRAME set as PARAM_VALUE from your init_param?
Martin 
______________________________________________ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem 
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. 
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung 
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le 
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez 
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est 
interdite. Ce message sert à l'information seulement et n'aura pas n'importe 
quel effet légalement obligatoire. Étant donné que les email peuvent facilement 
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité 
pour le contenu fourni.


> Date: Mon, 27 Aug 2012 12:47:26 +0530
> From: rathinasamy....@snovabits.net
> To: users@tomcat.apache.org
> Subject: Re: How-to-achieve-url-maxtry-filter-in-apache-tomcat
> 
> Hi,
> 
> Many thanks for your reply.
> 
> I am asking something which should be done in apache tomcat configurations, 
> Since I have not able to control that maxtry concept through my application 
> (it is out of my app control)
> 
> Through my app just generate a url to access a video file at run time, & may 
> be the user can copy that url and paste it in outside browsers - here I have 
> to control
> the usage of using my url which I have given to the user.
> 
> That url is something looks like 
> (http://localhost:8080/Club/dely/ios/item/42/23/cc.mp4) & it should accessed 
> via apache tomcat, so I am asking here for anyway to 
> expire the url path in apache tomcat using filters 
> 
> like:
> 
>  <init-param>
>     <param-name>ExpiresByType image</param-name>
>     <param-value>access plus 2 minutes</param-value>
>  </init-param>
>  <init-param>
> 
> But it expires image & after 2 minutes, I need to expires some url pattern 
> after 2 access.
> 
> Thank you again for spending your time in this.
> 
> Regards,
> Rathinasamy.
> 
> 
> On 8/27/2012 12:34 PM, Joseph wrote:
> > Have u tried to use regex to filter URL ,use concurrent hash map and atomic 
> > int to count?
> >
> > 在 2012-8-27,13:30,"rathinasamy....@snovabits.net" 
> > <rathinasamy....@snovabits.net> 写道:
> >
> >> Hi everyone,
> >>
> >> Please give me some ideas to achieve maxtry concept.
> >>
> >> I want to destroy the url path after some amount of access.
> >>
> >> For eg., if I give maxtry = 2 for the run time generated url 
> >> (http://localhost:8080/Club/dely/ios/item/42/23/cc.mp4), After the two 
> >> times access of the above url for the third time that url path will not be 
> >> able to access for anyone.
> >>
> >> _My environment is:_
> >>
> >> Apache-tomcat-7.0.25*
> >> *Windows 7
> >> 32 bit Operating system
> >>
> >> How to achieve this using apache filter?
> >>
> >> Thanks in advance,
> >> Rathinasamy.
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> > For additional commands, e-mail: users-h...@tomcat.apache.org
> >
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
> 
                                          

Reply via email to