Remove commercial TAS references from websockets and router troubleshooting topics [ai-assisted]

Made-with: Cursor

Author: anita-flegg

supporting-websockets.html.md.erb

@@ -39,8 +39,7 @@ To form a WebSocket connection, the client sends an HTTP request that contains a
   * Configure your load balancer to listen on a non-standard port (the built-in <%= vars.app_runtime_abbr %> load balancer listens on 8443 by default for this purpose), and forward requests for this port in TCP mode. App clients must make WebSockets upgrade requests to this port. If you choose this strategy, you must follow the steps in [Set Your Loggregator Port](#modify).
   * If a non-standard port is not acceptable, add a load balancer that handles WebSocket traffic (or another IP on an existing load balancer) and configure it to listen on standard ports 80 and 443 in TCP mode. Configure DNS with a new hostname, such as `ws.cf.example.com`, to be used for WebSockets. This hostname should resolve to the new load balancer interface.
 
-Regardless of your IaaS and configuration, you must configure your load balancer to send the X-Forwarded-For and X-Forwarded-Proto headers for non-WebSocket HTTP requests on ports 80 and 443. For more information, see <a href="https://docs.vmware.com/en/VMware-Tanzu-Application-Service/3.0/tas-for-vms/securing-traffic.html
-">Securing Traffic into TAS for VMs</a>.
+Regardless of your IaaS and configuration, you must configure your load balancer to send the X-Forwarded-For and X-Forwarded-Proto headers for non-WebSocket HTTP requests on ports 80 and 443.
 
 Gorouter supports WebSockets requests for routes that are bound to route services (routing-release version 0.339.0).
 

troubleshooting-router-error-responses.html.md.erb

@@ -252,8 +252,7 @@ You are more likely to have stale routes when the following are true:
 <% if vars.platform_code == 'CF' %>
 - You do not have Diego Release v2.34.0 or later deployed, which contains a fix that sends unregistration messages multiple times.
 <% else %>
-- You are on one of the versions of <%= vars.app_runtime_abbr %> that does not send deregister messages multiple times.
-For the list of versions, see [Enabling TLS from the Gorouter to application instances results in bad routes in TAS for VMs 2.3+](https://community.pivotal.io/s/article/enabling-tls-from-the-gorouter-to-application-instances-results-in-bad-routes?language=en_US) in the Knowledge Base.
+- You are on a version of <%= vars.app_runtime_abbr %> that does not send deregister messages multiple times.
 <% end %>
 - You unmapped a route to an app, but traffic to that route is still being sent to the app.