ansaurus

Question

Answer 1

A:

On the Java platform I use (sorry, not familiar with asp.net) we write our URLs using a utility method. This way the url rewriting can hook into that method and rewrite entire urls.

The advantage is that it can be done very efficiently. The disadvantage is that you can never just put a bare url in the HTML, you always have to use the helper method. However, for J2EE this is considered a normal best practice, so the overhead wasn't much in our case.

To implement the rewriting, we have a filter which wraps the http response and overrides the encodeURL method. I'm not sure if .net has a similar concept.

Mr. Shiny and New 2009-04-15 16:23:14

If .NET has a similar concept or if there is a better way to handle this, I am open to change. I would prefer to handle this in a filter so that we don't have to change every page in our website to wrap each URL. Seems like there should be a better solution.

2009-04-15 16:29:00

Answer 2

A:

If performance is critical, you may want to use your own implementation of a DFA scanner.

A tool to create the tables needed would be for instance the GOLD Parsing System (just skip the LALR stuff, which would process the grammar out of tokens found by the DFA scanner).

Lucero 2009-04-15 16:38:17

Answer 3

A:

How are your hyperlinks being generated? If you're using ASP.Net link controls to generate your URLs; you could just subclass the link control with a custom link control. This new link control, upon detecting the proxy, would rewrite your links on the fly; so the links are altered as needed before the HTML is even generated.

Frank Rosario 2009-04-19 19:14:16

ansaurus

tags:

views:

answers:

URL Rewriting in Response Filter

related questions