Results 1 to 3 of 3

Thread: RequestFilter, *, and absolute paths

  1. #1
    Join Date
    May 2013

    Default RequestFilter, *, and absolute paths

    It is possible to specify an absolute path - without any * - in <RequestFilters> for an HTTPProvider?

    I've tried things like:

    but that seems to yield warnings:

       WARN: HTTProvider2Base.QuickFilter: Cannot handle this filter: /foo/bar
    Adding in a * to the RequestFilter seems to solve the issue, but I'm curious if it's possible to perform an exact match in the filter.


  2. #2


    Can you please explain what it is you are trying to do? And why you need to use those characters?


  3. #3
    Join Date
    May 2013


    Lets say that I have an application that has multiple things to be exposed as HTTProviders. Each thing falls under a different path;


    One way would be to create a single "dispatcher" provider, with RequestFilters of foo/*. The filter would match the common root, and the provider would dispatch the correct thing based on the url path. This seems to work fine.

    The alternative would be to have one provider per url, and use the RequestFilters instead of explicitly dispatching with helper code. I wasn't able to get this working, as RequestFilters seemed to want a *.

    Not a big deal, just curious if I'm doing something horribly wrong


Similar Threads

  1. Multiple Content paths for a VOD streaming
    By ravikumarpinjala in forum General Forum
    Replies: 2
    Last Post: 11-04-2013, 01:01 PM
  2. MediaCache Can't Resolve HLS Paths
    By odrilon in forum Video On Demand Streaming Discussion
    Replies: 2
    Last Post: 02-15-2013, 11:00 AM
  3. Modules/Module/Class paths
    By newtriks in forum Wowza Media Server 3 for Amazon EC2 Discussion
    Replies: 7
    Last Post: 12-15-2011, 09:10 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts