Client-side URL rewriter
A system and method for client-side URL rewriting. In one embodiment the method comprises a client sending a request for content to a client proxy, wherein the request for content comprises a first URL. The client proxy may then rewrite the first URL and redirect the request for content to a reverse proxy server. In such an embodiment, the request for content may be sent to the client proxy based on a proxy configuration of the client. In a further aspect of the method above, rewriting the first URL with the client-side URL rewriter may comprise rewriting the request for content to a second URL, and including an indication of the first URL in the rewritten request for content. Furthermore, the first URL may correspond to an intranet server, while the second URL may correspond to the reverse proxy server.
1. A method, comprising:
a client sending an initial request for content to a reverse proxy connected to one or more intranet servers configured to serve the content;
in response to sending the initial request, receiving from the reverse proxy, data usable to implement a client-side URL rewriter, wherein the URL rewriter is operable to act as a client proxy for requests directed to any of the one or more intranet servers;
the client sending a request for content to the client-side URL rewriter, wherein the request for content comprises a URL identifying one of the intranet servers;
the client-side URL rewriter rewriting the URL, wherein the rewritten URL identifies the reverse proxy;
the client-side URL rewriter sending a redirect response code with the rewritten URL back to the same client that sent the request to the client-side URL rewriter; and
in response to receiving the rewritten URL and redirect response code, the same client redirecting the request for content to the reverse proxy indicated by the rewritten URL, wherein the redirected request is not sent to the URL rewriter.
2. The method of claim 1 , wherein the client is configured so that all requests for content having a URL corresponding to the intranet server are sent to a client proxy comprising the client-side URL rewriter.
3. The method of claim 2 , wherein the request for content is sent to the client proxy based on a proxy auto-configuration (PAC) of a browser application on the client.
4. The method of claim 1 further comprising, in response to receiving the data usable to implement the client-side URL rewriter, installing the client-side URL rewriter on a computer separate from the client.
5. The method of claim 1 , wherein the rewritten URL includes an indication of the URL.
6. The method of claim 1 , wherein the client-side URL rewriter is responsive to requests from the client and from one or more other clients over a client-side network.
7. The method of claim 1 , wherein the method further comprises:
the reverse proxy server retrieving content from an intranet server in accordance with the request for content; and
the reverse proxy server returning said content to the client.
8. The method of claim 1 , wherein redirecting the request for content to a reverse proxy server comprises:
a client proxy comprising the client-side URL rewriter returning the rewritten URL to a browser; and
the client proxy sending a redirect command to the browser.
9. A computer system, comprising:
a processor;
memory coupled to the processor and storing program instructions executable by the processor to implement:
a client sending an initial request for content to a reverse proxy connected to one or more intranet servers configured to serve the content;
in response to sending the request, receiving from the reverse proxy, data usable to implement a client-side URL rewriter, wherein the URL rewriter is operable to act as a client proxy for requests directed to any of the one or more intranet servers;
the client sending a request for content to the client-side URL rewriter, wherein the request for content comprises a URL identifying one of the intranet servers;
the client-side URL rewriter rewriting the URL, wherein the rewritten URL identifies the reverse proxy;
the client-side URL rewriter sending a redirect response code with the rewritten URL back to the same client that sent the request to the client-side URL rewriter; and
in response to receiving the rewritten URL and redirect response code, the same client redirecting the request for content to the reverse proxy indicated by the rewritten URL, wherein the redirected request is not sent to the URL rewriter.
10. The system of claim 9 , wherein the client is configured to send all requests for content having URLs corresponding to the intranet server to a client proxy comprising the client-side URL rewriter.
11. The system of claim 10 , further comprising a proxy auto-configuration (PAC) file configured to indicate that the request for content should be sent to the client proxy from a browser application on the client.
12. The system of claim 9 , wherein the client-side URL rewriter is installed on a computer separate from the client.
13. The system of claim 9 , wherein the rewritten URL includes an indication of the URL.
14. The system of claim 9 , wherein the client-side URL rewriter is responsive to requests from the client and from one or more other clients over a client-side network.
15. The system of claim 9 , wherein the reverse proxy server is further configured to:
retrieve the content identified by the request for content, from the intranet server; and
return the identified content to the client.
16. The system of claim 9 , wherein the client-side URL rewriter is operable to redirect the request for content to a reverse proxy server by:
returning the rewritten first URL to a browser; and
sending a redirect command to the browser.
17. A non-transitory computer accessible storage medium storing program instructions computer executable to implement a method comprising:
a client sending an initial request for content to a reverse proxy connected to one or more intranet servers configured to serve the content;
in response to sending the initial request, receiving from the reverse proxy, data usable to implement a client-side URL rewriter, wherein the URL rewriter is operable to act as a client proxy for requests directed to any of the one or more intranet servers;
the client sending a request for content to the client-side URL rewriter, wherein the request for content comprises a URL identifying one of the intranet servers;
the client-side URL rewriter rewriting the URL, wherein the rewritten URL identifies the reverse proxy server;
the client-side URL rewriter sending a redirect response code with the rewritten URL back to the same client that sent the request to the client-side URL rewriter; and
in response to receiving the rewritten URL and redirect response code, the same client redirecting the request for content to the reverse proxy indicated by the rewritten URL, wherein the redirected request is not sent to the URL rewriter.
18. The computer accessible medium of claim 17 , wherein the client is configured so that requests for content comprising URLs corresponding to the intranet server are sent to a client proxy comprising the client-side URL rewriter.
19. The computer accessible medium of claim 18 , wherein the request for content is sent to the client proxy based on a proxy auto-configuration (PAC) of a browser application on the client.
20. The computer accessible medium of claim 17 , wherein the client-side URL rewriter is installed on a computer separate from the client.
21. The computer accessible medium of claim 17 , wherein the rewritten URL includes an indication of the URL.
22. The computer accessible medium of claim 21 , wherein the client-side URL rewriter is responsive to requests from the client and from one or more other clients over a client-side network.
23. The computer accessible medium of claim 17 , wherein redirecting the request for content to a reverse proxy server comprises:
the client-side URL rewriter returning the rewritten first URL to a browser; and
the client-side URL rewriter sending a redirect command to the browser.