However, for Pulse, the using the similar setup from the guide “works”, but when login or logout from Pulse would then failed and sort of returned a 404, as the redirect triggering from Pulse still pointing to the incorrect URL, the one before Reverse Proxy configured.

Pulse is redirecting on the server and therefore doesn’t know about the proxy address you have placed in front of it. If there is a header with the proxy address we could use that to redirect to instead. If you can find out want headers IIS sets would could look into it further.

Been going through a number of websites already trying to configure that, it’s either making Pulse completely down or it just didn’t apply, and the problem is it is only happening on Login and Logout, the other functions are fine.