# One VIP, several websites **URL:** \ **Category:** aFleX\ **Created:** [May 18, 2017, 2:48pm UTC](https://community.a10networks.com/t/one-vip-several-websites/449 "2017-05-18T14:48:02Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![andimorris](https://avatars.discourse-cdn.com/v4/letter/a/858c86/32.png) [@andimorris](https://community.a10networks.com/u/andimorris)\ **Post date:** [May 18, 2017, 2:48pm UTC](https://community.a10networks.com/t/one-vip-several-websites/449/1 "2017-05-18T14:48:02Z")
Hi all, apologies for cross posting. I think this might get more luck in the AFlex forum rather than the General forum. can somebody please advise me on the best approaches for the following two scenarios? I can’t figure out whether aflex, http filters, WAF, or a combination of the three are the way to go. Scenario 1: One VIP reverse proxying one web server. This web server has several different websites with differing URLS (e.g [website1.domain.com](http://website1.domain.com), [website2.domain.com](http://website2.domain.com)), using a mixture of http and https. If possible I’d like the A10 to only allow access to specific URLS. Scenario 2: One VIP reverse proxying one web server. The web server has several different websites with differing paths (e.g. [website.domain.com/path1](http://website.domain.com/path1) [website.domain.com/path2](http://website.domain.com/path2)). All of which are https through to the server. Again I’d like A10 to restrict the paths available. Any advice would be appreciated. ---
**Author:** ![diederik](https://avatars.discourse-cdn.com/v4/letter/d/a587f6/32.png) [@diederik](https://community.a10networks.com/u/diederik)\ **Post date:** [May 19, 2017, 4:16pm UTC](https://community.a10networks.com/t/one-vip-several-websites/449/2 "2017-05-19T16:16:46Z")
For Scenario 1, how exactly do you want to limit access? You can use an HTTP template and use host switching, don’t set a default servicegroup in the config and based on the “host header” only the hostnames specified in your host switching config will be allowed. On the HTTPS side, this template will also get applied, but only after the SSL session is established. If you want to block “SSL” connections to hostnames that you do not host or specific ones you want to block, you need to use SNI hooks in aFlex. For scenario 2, if you just want to filter paths, and the hostname is the same, you can use “Application Switching”… similar to “Host Switching” also in the HTTP Template. You can’t use host and app switching together in the same template. For host and app switching together I would use aFlex… switch on Host followed by a switch on URI. ---
**Author:** ![system](https://us1.discourse-cdn.com/flex002/uploads/a10_community/original/1X/bb9f186d33804d3044a0374e589f49fdf3be1328.png) [@system](https://community.a10networks.com/u/system)\ **Post date:** [June 22, 2017, 3:17pm UTC](https://community.a10networks.com/t/one-vip-several-websites/449/3 "2017-06-22T15:17:33Z")
You can do it also with AFLEX and class list.