Forum Discussion
iRule to hide internal URL from users
so first and foremost, i'm having trouble getting the 1st piece taken care of... with an iRule to get the redirect and/or rewrite to take place... i'm a noob and this is my 1st post. i'm on v11, APM & ASM and am going to a training class next week, just trying to get some tasks accomplished prior...
i'm guessing i'll need a redirect or host replacement for incoming traffic, and then some kind of rewrite on the response to the client because internal.domain.com is not in public dns? I'm hoping the rewrite will take care of relative URLs?...
thanks...
- hooleylistCirrostratusHi,
- gh0std0g_79292NimbostratusYes, we have to restrict access for security reasons... So external users should only be able to get to URIs below their 'sales' page:
- hooleylistCirrostratusSorry I missed your reply here. It's not really feasible (read: effective and efficient) to use iRules to do directory restrictions for IIS, due to the number of ways that IIS accepts URIs. See this post for examples of why:
- hooleylistCirrostratusAnd I forgot to mention, ASM is an effective way to enforce path restrictions. ASM is able to normalize the different encoding methods a malicious user could try to bypass restrictions with. It should be fairly straightforward to do this within ASM. Note that if you use ProxyPass on an ASM virtual server, the hostnames and/or URIs ASM gets will have already been rewritten by ProxyPass.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com