Simply, i want to remove the extension page :)
"Googling" a little bit i've found this link :
http://forums.asp.net/p/1027180/1408446.aspx
and seems that my request needs a lot of work under the hood for a,
apparently, simple feature :(
Any suggestion?
Sorry for the (maybe) OT
I wrote about this here:
http://joshrobb.com/blog/2007/04/26/monorail-url-rewriting/
Short version is that this is something that requires changes to IIS
configuration and a third party ISAPI filter.
j.
On 31 Ago, 14:02, "Colin Ramsay" <colinram...@gmail.com> wrote:
> And here's a bit I wrote about URL rewriting options on IIS:
>
> http://colinramsay.co.uk/2007/04/17/url-rewriting-options-on-iis/
>
> On 8/31/07, josh robb <josh_r...@fastmail.fm> wrote:
>
>
>
>
>
> > > Simply, i want to remove the extension page :)
>
> > > "Googling" a little bit i've found this link :
> > >http://forums.asp.net/p/1027180/1408446.aspx
> > > and seems that my request needs a lot of work under the hood for a,
> > > apparently, simple feature :(
>
> > I wrote about this here:
> >http://joshrobb.com/blog/2007/04/26/monorail-url-rewriting/
>
> > Short version is that this is something that requires changes to IIS
> > configuration and a third party ISAPI filter.
>
> > j.- Nascondi testo tra virgolette -
>
> - Mostra testo tra virgolette -
I really like mod_rewrite, but as you can see it requires 3rd party
components also.
The easiest thing is to use what you already have at your fingertips with
IIS, ASP.NET
and MonoRail itself, and route all requests through ASP.NET.
Then, you can use the MonoRail URL rewriting features within web.config.
Now performance-wise, you don't want to route requests through the
ASP.NET/MonoRail stack
for things such as .css files, image resources etc.
What I do for this is that I map the URLs for all static resources to
another
virtual directory which is purely IIS serving up these files.
I.e. I make the $static variable available in all my NVelocity templates,
and if I
insert an image it looks like this: <img src="$static/images/image.gif"/>
as a
simple example.
This currently resolves to http://localhost/static/images/image.gif, with
/static
being a virtual directory, and within there all my static content (css,
javascript,
images etc).
This is very scalable in that in a production environment, we can change
our $static
to point to http://static.ourdomain.com and have light and fast web
servers such as
lighttpd or just a vanilla IIS serving up our static content fast, easing
the load
on a dedicated application server.
So in summary, I evaluated mod_rewrite-style alternatives and went with
the simple
solution built into MonoRail, and implemented a good practice of having a
separate
URL for static content which is going to make our application more
scalable in the
future anyway.
--
David Moore
Ziymoo
South Bank House
Black Prince Road
London, SE1 7SJ
T (020) 7793 2366
--
Cheers,
hamilton verissimo
ham...@castlestronghold.com
http://www.castlestronghold.com/
Writing this made me think I should write a more detailed blog about it
and also the other things I've done
using Castle for the first time with a reasonably ambitious project. If
you like I can write something a bit
more detailed and step-by-step with actual code and config if that's more
suitable.
For now, I'll add the comments to the routing doc on the official documentation.
Thanks
One good thing with that solution is that you can set up the web app in
either way (1 or 2 virtual directories). You could set $static to $siteRoot
and use another set of routing rules with a different UrlBuilder so people
that only want to set up a single virtual directory can use the same app
without modification.
I'm really liking this solution and I'm wondering why no one else thought of
this solution ages ago ;-)
Regards, Jonathon Rossi
It's actually widely discussed :)
See the 2nd rule of Yahoo's "Thirteen Simple Rules for Speeding Up
Your Web Site":
http://developer.yahoo.com/performance/rules.html#cdn
--
Fábio David Batista
fabio.dav...@gmail.com
http://nerd-o-matic.blogspot.com