# APM as an RDP Proxy but still get to RD Web Access page?

**URL:** <https://community.f5.com/t/apm-as-an-rdp-proxy-but-still-get-to-rd-web-access-page/27700>\
**Category:** Technical Forums\
**Tags:** iapps, big-ip-access-policy-manager-apm, application-delivery\
**Created:** [December 2, 2016, 5:53pm UTC](https://community.f5.com/t/apm-as-an-rdp-proxy-but-still-get-to-rd-web-access-page/27700 "2016-12-02T17:53:13Z")\
**Posts on this page:** 1\
**Showing post:** 20

<div class="post-metadata">

**Author:** ![LeeH](https://avatars.discourse-cdn.com/v4/letter/l/e47c2d/32.png) [@LeeH](https://community.f5.com/u/LeeH)\
**Post date:** [April 28, 2017, 5:14pm UTC](https://community.f5.com/t/apm-as-an-rdp-proxy-but-still-get-to-rd-web-access-page/27700/20 "2017-04-28T17:14:55Z")

</div>

I should also mention that I think the RDP client is being classified properly. The line before the 2 log lines I pasted is this:

```tcl
Apr 27 15:04:48 F5-APM-V2 debug tmm[11517]: 019cffff:7: /Common/RDITAccessPolicy:Common:00000000: Client-type (rdg-http)

```

Another thing I have noticed in our production APM logs which may or may not be related is we are seeing F5 cookie info from our LTM showing up in the logs. The only thing running on our APM box at the moment is our Remote Desktop related stuff. Not sure if that extra stuff in the cookie might be confusing things. That would be something else that is different in production.

---

_[View the full topic](https://community.f5.com/t/apm-as-an-rdp-proxy-but-still-get-to-rd-web-access-page/27700)._
