Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon5.gif   Isolating search urls, posted by Philip Leung on Wed Aug 12 16:59:30 2015 
    icon2.gif   Re: Isolating search urls, posted by Stefan Ritt on Wed Aug 12 17:19:45 2015 
       icon2.gif   Re: Isolating search urls, posted by Philip Leung on Thu Aug 13 10:06:23 2015 
          icon2.gif   Re: Isolating search urls, posted by Philip Leung on Mon Aug 17 10:32:51 2015 
             icon2.gif   Re: Isolating search urls, posted by Stefan Ritt on Mon Aug 17 10:41:22 2015 
                icon2.gif   Re: Isolating search urls, posted by Philip Leung on Mon Aug 17 11:17:37 2015 
                   icon2.gif   Re: Isolating search urls, posted by Stefan Ritt on Mon Aug 17 11:26:22 2015 
                      icon2.gif   Re: Isolating search urls, posted by Philip Leung on Mon Aug 17 11:28:08 2015 
                         icon2.gif   Re: Isolating search urls, posted by Stefan Ritt on Mon Aug 17 11:36:49 2015 
                            icon2.gif   Re: Isolating search urls, posted by Philip Leung on Mon Aug 17 11:52:54 2015 
Message ID: 68078     Entry time: Wed Aug 12 16:59:30 2015     Reply to this: 68079
Icon: Question  Author: Philip Leung  Author Email: philip.leung@cern.ch 
Category: Question  OS: Linux | Windows  ELOG Version: 3.1.1 
Subject: Isolating search urls 

Hello all,

I am in need of isolating GET-requests referring to long-running, read-only elog functions such as search/filter/sort in our Apache proxy and redirecting them elsewhere. There does not, however, appear to be any easy way of reliably isolating these functions (with the exception of sort) by only looking at the URL.

Does anybody have any suggestions?

Regards,

Philip

ELOG V3.1.5-fe60aaf