View previous topic :: View next topic |
Author |
Message |
Nonapeptide
Joined: 08 Sep 2012 Posts: 40 Location: Scottsdale, Arizona
|
Posted: Mon Aug 26, 2013 10:05 pm Post subject: Possible to take action based on referring URL? |
|
|
I have a situation where an IceCast server would ideally deny connections based on referring URL. There should be only one domain that can link people to the server. Currently I'm thinking I could make some kind of front end Apache proxy server that has a set of rules concerning referring URLs and destinations. Rewrites to the backend IceCast servers would be granted or disallowed based on the rules I set out.
However, just to make sure I'm not missing something obvious, is there some way of making that a reality using IceCast's KH branch alone? |
|
Back to top |
|
|
karlH Code Warrior
Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Tue Sep 03, 2013 2:08 am Post subject: |
|
|
I missed this post, sorry for not getting back.
auth url passes the listeners referer in the POST for listener_add, you can use that as test condition for returning the icecast-auth-user header or not. You can also return a Location: header to redirect them elsewhere or a Mountpoint: header to send then to another stream/file on the same icecast. Each requires a 200 OK response.
karl. |
|
Back to top |
|
|
Nonapeptide
Joined: 08 Sep 2012 Posts: 40 Location: Scottsdale, Arizona
|
Posted: Tue Sep 03, 2013 2:37 am Post subject: |
|
|
karlH wrote: |
I missed this post, sorry for not getting back.
auth url passes the listeners referer in the POST for listener_add, you can use that as test condition for returning the icecast-auth-user header or not. You can also return a Location: header to redirect them elsewhere or a Mountpoint: header to send then to another stream/file on the same icecast. Each requires a 200 OK response.
karl. |
Ohhhhh, okay. Yes, I recall reading about this but it didn't "click" because I had no reason to use it at the time. I'll look into that! |
|
Back to top |
|
|
|