Sì....
In pratica il ProxyPass dice che se arriva al server A una richiesta per wss2 la deve girare al server B (ws:miosito ecc). Il server B elabora il tutto MA se sul server B c'è qualche percorso assoluto si creano casini perchè la risposta che ti darà A sarà relativa ad A e non a B

Dal manuale Apache
For example, suppose the local server has address http://example.com/; then


ProxyPass "/mirror/foo/" "http://backend.example.com/"
ProxyPassReverse "/mirror/foo/" "http://backend.example.com/"
ProxyPassReverseCookieDomain "backend.example.com" "public.example.com"
ProxyPassReverseCookiePath "/" "/mirror/foo/"


will not only cause a local request for the http://example.com/mirror/foo/bar to be internally converted into a proxy request to http://backend.example.com/bar (the functionality which ProxyPass provides here). It also takes care of redirects which the server backend.example.com sends when redirecting http://backend.example.com/bar to http://backend.example.com/quux . Apache httpd adjusts this to http://example.com/mirror/foo/quux before forwarding the HTTP redirect response to the client. Note that the hostname used for constructing the URL is chosen in respect to the setting of the UseCanonicalName directive.