# Restrict access to Live HTTP Origin application **URL:** \ **Category:** Wowza Streaming Engine\ **Created:** [February 16, 2016, 10:40am UTC](https://community.wowza.com/t/restrict-access-to-live-http-origin-application/33633 "2016-02-16T10:40:20Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Karel\_Boek](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/karel_boek/32/454_2.png) [@Karel\_Boek](https://community.wowza.com/u/Karel_Boek)\ **Post date:** [February 16, 2016, 10:40am UTC](https://community.wowza.com/t/restrict-access-to-live-http-origin-application/33633/1 "2016-02-16T10:40:20Z")
We have a Wowza server configured with a Live HTTP Origin application, and a number of non-Wowza edge servers running Varnish. We want to make sure that only the edge servers can access the origin. Because of Origin Mode in the application, all outgoing connections share session, thus it’s not possible to use the Client Restrictions as described in [https://www.wowza.com/docs/how-to-configure-security-using-wowza-streaming-engine-manager](https://www.wowza.com/docs/how-to-configure-security-using-wowza-streaming-engine-manager), or use onHTTPSessionCreate for that matter. We can’t use IPTables to block unknown IP addresses, because we don’t know the IPs of incoming RTMP streams, who use the same port. Any suggestions on how we can restrict access to the HTTP streams, so that only our own edge servers can pull the chunks? ---
**Author:** ![Andrew\_Kennedy1](https://avatars.discourse-cdn.com/v4/letter/a/278dde/32.png) [@Andrew\_Kennedy1](https://community.wowza.com/u/Andrew_Kennedy1)\ **Post date:** [February 28, 2016, 12:40pm UTC](https://community.wowza.com/t/restrict-access-to-live-http-origin-application/33633/2 "2016-02-28T12:40:51Z")
Hi, You can use the interface IVHostHTTPStreamerRequestValidator. This provides access to all HTTP requests inbound. Andrew