Server.Transfer to ASP.old pages?

[Jon Sequeira]

Is there a way to redirect from an ASP.NET page to an ASP page without
showing the ASP page's URL in the client's browser?

This works perfectly with an HTML page, for example:

path = "~/cp/test.htm"
Server.Transfer(path, False)

But with an .asp extension, the I get an HttpException, "Error executing
child request for ~/cp/test.asp."

I suppose the ASP.NET page factory is trying to execute the ASP page.

If anyone has suggestions on another way to accomplish this, I'm very
curious.

Thanks.

--Jon

[Kevin Spencer]

Try Response.Redirect. Server.Transfer works within the ASP.Net ISAPI, and
can never work with ASP pages. Response.Redirect sends a redirect request to
the browser, which then requests the ASP page appropriately.

HTH,

Kevin Spencer
Microsoft FrontPage MVP
Internet Developer
[url]http://www.takempis.com[/url]
Big things are made up of
lots of Little things.

"Jon Sequeira" <jsequeir@twcny.rr.com> wrote in message
news:u0ESV0xPDHA.1556@TK2MSFTNGP10.phx.gbl...

> Is there a way to redirect from an ASP.NET page to an ASP page without
> showing the ASP page's URL in the client's browser?
>
> This works perfectly with an HTML page, for example:
>
> path = "~/cp/test.htm"
> Server.Transfer(path, False)
>
> But with an .asp extension, the I get an HttpException, "Error executing
> child request for ~/cp/test.asp."
>
> I suppose the ASP.NET page factory is trying to execute the ASP page.
>
> If anyone has suggestions on another way to accomplish this, I'm very
> curious.
>
> Thanks.
>
> --Jon
>
>
>

[Kevin Spencer]

Hi Ted,

I thought so too at first. However, if you look at my second response, I
think you'll agree that I've come up with a solution that should work.

HTH,

Kevin Spencer
Microsoft FrontPage MVP
Internet Developer
[url]http://www.takempis.com[/url]
Big things are made up of
lots of Little things.

"Ted" <commcorpVERWIJDER@DIThotmail.com> wrote in message
news:3f007938$0$28903$1b62eedf@news.euronet.nl...

> "Jon Sequeira" <jsequeir@twcny.rr.com> wrote in message
> news:e29AE6yPDHA.2480@tk2msftngp13.phx.gbl...

> > Thanks.
> >
> > I'm looking for a way to do it without Response.Redirect-- I'd like the
> > redirect to take place on the server, without the browser seeing the new
> > URL. The intention here is to create a similar effect to an URL

rewriter,

> so

> > that site users and search engines are not aware of the second, target

> URL,

> > which contains a number of query string parameters that I don't wish to
> > expose.
> >
> > Any ideas are appreciated.
> >
> > --Jon
> >

>
> This is not possible. Also because Server.Redirect in ASP will not accept
> 'new' querystring parameters, only the ones that were sent by the browser
> with the original request are available.
>
> Ted
>
>

[Jon Sequeira]

This is almost working. It does serve up the desired page, but THAT page is
a bit crippled. Its form doesn't submit properly (the stack trace shops an
HttpException being thrown on System.Web.HttpApplication.MapHttpHandler),
and the served page's CSS is missing.

Do you have any sense of how easily these issues can be dealt with? (In a
pure ASP.NET scheme, I can implement an URL rewriter using an HttpModule and
I think it will be pretty simple. Since these ASP pages need to be rewritten
eventually anyway, I'm considering skipping right to that step.)

Thanks for your input.

--Jon

"Kevin Spencer" <kevin@SPAMMERSSUCKtakempis.com> wrote in message
news:e7PLnRzPDHA.2460@TK2MSFTNGP10.phx.gbl...

> Well, there is one way that I can think of. On the server side, you can
> create a WebRequest, which is an HTTP request for a resource. The

WebRequest

> can request the ASP page, which invokes the ASP ISAPI on the web server to
> handle that request. The HTML Response from that Request can then be
> returned to the browser using Response.Write from the ASP.Net Page class.
>
> HTH,
>
> Kevin Spencer
> Microsoft FrontPage MVP
> Internet Developer
> [url]http://www.takempis.com[/url]
> Big things are made up of
> lots of Little things.
>
> "Jon Sequeira" <jsequeir@twcny.rr.com> wrote in message
> news:e29AE6yPDHA.2480@tk2msftngp13.phx.gbl...

> > Thanks.
> >
> > I'm looking for a way to do it without Response.Redirect-- I'd like the
> > redirect to take place on the server, without the browser seeing the new
> > URL. The intention here is to create a similar effect to an URL

rewriter,

> so

> > that site users and search engines are not aware of the second, target

> URL,

> > which contains a number of query string parameters that I don't wish to
> > expose.
> >
> > Any ideas are appreciated.
> >
> > --Jon
> >
> >
> > "Kevin Spencer" <kevin@SPAMMERSSUCKtakempis.com> wrote in message
> > news:#Cby0pyPDHA.1584@TK2MSFTNGP11.phx.gbl...

> > > Try Response.Redirect. Server.Transfer works within the ASP.Net ISAPI,

> and

> > > can never work with ASP pages. Response.Redirect sends a redirect

> request

> > to

> > > the browser, which then requests the ASP page appropriately.
> > >
> > > HTH,
> > >
> > > Kevin Spencer
> > > Microsoft FrontPage MVP
> > > Internet Developer
> > > [url]http://www.takempis.com[/url]
> > > Big things are made up of
> > > lots of Little things.
> > >
> > > "Jon Sequeira" <jsequeir@twcny.rr.com> wrote in message
> > > news:u0ESV0xPDHA.1556@TK2MSFTNGP10.phx.gbl...
> > > > Is there a way to redirect from an ASP.NET page to an ASP page

without

> > > > showing the ASP page's URL in the client's browser?
> > > >
> > > > This works perfectly with an HTML page, for example:
> > > >
> > > > path = "~/cp/test.htm"
> > > > Server.Transfer(path, False)
> > > >
> > > > But with an .asp extension, the I get an HttpException, "Error

> executing

> > > > child request for ~/cp/test.asp."
> > > >
> > > > I suppose the ASP.NET page factory is trying to execute the ASP

page.

> > > >
> > > > If anyone has suggestions on another way to accomplish this, I'm

very

> > > > curious.
> > > >
> > > > Thanks.
> > > >
> > > > --Jon
> > > >
> > > >
> > > >
> > >
> > >

> >
> >

>
>

[Kevin Spencer]

I see what you mean. I believe this could be fairly easily accomplished, as
you know the path to the requested file, and the path to the current file.
From there, it is a (fairly) simple matter of parsing the string returned in
the Response from the WebRequest, and replacing relative paths with absolute
paths. You should be able to locate and Replace the URLs using Regular
Expressions.

HTH,

Kevin Spencer
Microsoft FrontPage MVP
Internet Developer
[url]http://www.takempis.com[/url]
Big things are made up of
lots of Little things.

"Jon Sequeira" <jsequeir@twcny.rr.com> wrote in message
news:OdkN7l$PDHA.2036@TK2MSFTNGP10.phx.gbl...

> Sorry, my post was a bit confusing. I was doing a test-of-theory by
> referring to an ASP.NET page, to take advantage of the debugger (and

because

> I'm trying to find a solution that won't need to be extensively rewritten
> when the whole site is migrated to ASP.NET).
>
> I think the problem is that for the page to be served correctly via a

second

> HttpWebRequest, all of the relative links in the served page need to be
> replaced with absolute URLs. Otherwise the page's form won't work, and
> graphics and CSSs and includes can't be found, and so on.
>
> At this point, rewriting the ASP page to be served this way may be nearly

as

> much work as reimplementing it in ASP.NET. Unless I'm missing something.
>
> Regards,
>
> --Jon
>
> "Kevin Spencer" <kevin@SPAMMERSSUCKtakempis.com> wrote in message
> news:ueIv7Q$PDHA.2228@tk2msftngp13.phx.gbl...

> > As the ASP page in the browser is pure HTML, I have no idea what you're
> > referring to when you say "a bit crippled" and I have no idea what

"stack

> > trace" you're referring to. From your description, the "stack trace" is

a

> > stack trace from an ASP.Net application. So I'm at a loss as to what

> you're

> > describing here.
> >
> > HTH,
> >
> > Kevin Spencer
> > Microsoft FrontPage MVP
> > Internet Developer
> > [url]http://www.takempis.com[/url]
> > Big things are made up of
> > lots of Little things.
> >
> > "Jon Sequeira" <jsequeir@twcny.rr.com> wrote in message
> > news:eMGkO39PDHA.2768@tk2msftngp13.phx.gbl...

> > > This is almost working. It does serve up the desired page, but THAT

page

> > is

> > > a bit crippled. Its form doesn't submit properly (the stack trace

shops

> an

> > > HttpException being thrown on

> System.Web.HttpApplication.MapHttpHandler),

> > > and the served page's CSS is missing.
> > >
> > > Do you have any sense of how easily these issues can be dealt with?

(In

> a

> > > pure ASP.NET scheme, I can implement an URL rewriter using an

HttpModule

> > and

> > > I think it will be pretty simple. Since these ASP pages need to be

> > rewritten

> > > eventually anyway, I'm considering skipping right to that step.)
> > >
> > > Thanks for your input.
> > >
> > > --Jon
> > >
> > > "Kevin Spencer" <kevin@SPAMMERSSUCKtakempis.com> wrote in message
> > > news:e7PLnRzPDHA.2460@TK2MSFTNGP10.phx.gbl...
> > > > Well, there is one way that I can think of. On the server side, you

> can

> > > > create a WebRequest, which is an HTTP request for a resource. The
> > > WebRequest
> > > > can request the ASP page, which invokes the ASP ISAPI on the web

> server

> > to

> > > > handle that request. The HTML Response from that Request can then be
> > > > returned to the browser using Response.Write from the ASP.Net Page

> > class.

> > > >
> > > > HTH,
> > > >
> > > > Kevin Spencer
> > > > Microsoft FrontPage MVP
> > > > Internet Developer
> > > > [url]http://www.takempis.com[/url]
> > > > Big things are made up of
> > > > lots of Little things.
> > > >
> > > > "Jon Sequeira" <jsequeir@twcny.rr.com> wrote in message
> > > > news:e29AE6yPDHA.2480@tk2msftngp13.phx.gbl...
> > > > > Thanks.
> > > > >
> > > > > I'm looking for a way to do it without Response.Redirect-- I'd

like

> > the

> > > > > redirect to take place on the server, without the browser seeing

the

> > new

> > > > > URL. The intention here is to create a similar effect to an URL
> > > rewriter,
> > > > so
> > > > > that site users and search engines are not aware of the second,

> target

> > > > URL,
> > > > > which contains a number of query string parameters that I don't

wish

> > to

> > > > > expose.
> > > > >
> > > > > Any ideas are appreciated.
> > > > >
> > > > > --Jon
> > > > >
> > > > >
> > > > > "Kevin Spencer" <kevin@SPAMMERSSUCKtakempis.com> wrote in message
> > > > > news:#Cby0pyPDHA.1584@TK2MSFTNGP11.phx.gbl...
> > > > > > Try Response.Redirect. Server.Transfer works within the ASP.Net

> > ISAPI,

> > > > and
> > > > > > can never work with ASP pages. Response.Redirect sends a

redirect

> > > > request
> > > > > to
> > > > > > the browser, which then requests the ASP page appropriately.
> > > > > >
> > > > > > HTH,
> > > > > >
> > > > > > Kevin Spencer
> > > > > > Microsoft FrontPage MVP
> > > > > > Internet Developer
> > > > > > [url]http://www.takempis.com[/url]
> > > > > > Big things are made up of
> > > > > > lots of Little things.
> > > > > >
> > > > > > "Jon Sequeira" <jsequeir@twcny.rr.com> wrote in message
> > > > > > news:u0ESV0xPDHA.1556@TK2MSFTNGP10.phx.gbl...
> > > > > > > Is there a way to redirect from an ASP.NET page to an ASP page
> > > without
> > > > > > > showing the ASP page's URL in the client's browser?
> > > > > > >
> > > > > > > This works perfectly with an HTML page, for example:
> > > > > > >
> > > > > > > path = "~/cp/test.htm"
> > > > > > > Server.Transfer(path, False)
> > > > > > >
> > > > > > > But with an .asp extension, the I get an HttpException, "Error
> > > > executing
> > > > > > > child request for ~/cp/test.asp."
> > > > > > >
> > > > > > > I suppose the ASP.NET page factory is trying to execute the

ASP

> > > page.
> > > > > > >
> > > > > > > If anyone has suggestions on another way to accomplish this,

I'm

> > > very
> > > > > > > curious.
> > > > > > >
> > > > > > > Thanks.
> > > > > > >
> > > > > > > --Jon
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >

> >
> >

>
>

[Jon Sequeira]

Thanks. This should definitely work.

I appreciate your help.

--Jon

"Kevin Spencer" <kevin@SPAMMERSSUCKtakempis.com> wrote in message
news:Ob#MLdAQDHA.2228@tk2msftngp13.phx.gbl...

> I see what you mean. I believe this could be fairly easily accomplished,

as

> you know the path to the requested file, and the path to the current file.
> From there, it is a (fairly) simple matter of parsing the string returned

in

> the Response from the WebRequest, and replacing relative paths with

absolute

> paths. You should be able to locate and Replace the URLs using Regular
> Expressions.
>
> HTH,
>
> Kevin Spencer
> Microsoft FrontPage MVP
> Internet Developer
> [url]http://www.takempis.com[/url]
> Big things are made up of
> lots of Little things.
>
> "Jon Sequeira" <jsequeir@twcny.rr.com> wrote in message
> news:OdkN7l$PDHA.2036@TK2MSFTNGP10.phx.gbl...

> > Sorry, my post was a bit confusing. I was doing a test-of-theory by
> > referring to an ASP.NET page, to take advantage of the debugger (and

> because

> > I'm trying to find a solution that won't need to be extensively

rewritten

> > when the whole site is migrated to ASP.NET).
> >
> > I think the problem is that for the page to be served correctly via a

> second

> > HttpWebRequest, all of the relative links in the served page need to be
> > replaced with absolute URLs. Otherwise the page's form won't work, and
> > graphics and CSSs and includes can't be found, and so on.
> >
> > At this point, rewriting the ASP page to be served this way may be

nearly

> as

> > much work as reimplementing it in ASP.NET. Unless I'm missing something.
> >
> > Regards,
> >
> > --Jon
> >
> > "Kevin Spencer" <kevin@SPAMMERSSUCKtakempis.com> wrote in message
> > news:ueIv7Q$PDHA.2228@tk2msftngp13.phx.gbl...

> > > As the ASP page in the browser is pure HTML, I have no idea what

you're

> > > referring to when you say "a bit crippled" and I have no idea what

> "stack

> > > trace" you're referring to. From your description, the "stack trace"

is

> a

> > > stack trace from an ASP.Net application. So I'm at a loss as to what

> > you're

> > > describing here.
> > >
> > > HTH,
> > >
> > > Kevin Spencer
> > > Microsoft FrontPage MVP
> > > Internet Developer
> > > [url]http://www.takempis.com[/url]
> > > Big things are made up of
> > > lots of Little things.
> > >
> > > "Jon Sequeira" <jsequeir@twcny.rr.com> wrote in message
> > > news:eMGkO39PDHA.2768@tk2msftngp13.phx.gbl...
> > > > This is almost working. It does serve up the desired page, but THAT

> page

> > > is
> > > > a bit crippled. Its form doesn't submit properly (the stack trace

> shops

> > an

> > > > HttpException being thrown on

> > System.Web.HttpApplication.MapHttpHandler),

> > > > and the served page's CSS is missing.
> > > >
> > > > Do you have any sense of how easily these issues can be dealt with?

> (In

> > a

> > > > pure ASP.NET scheme, I can implement an URL rewriter using an

> HttpModule

> > > and
> > > > I think it will be pretty simple. Since these ASP pages need to be
> > > rewritten
> > > > eventually anyway, I'm considering skipping right to that step.)
> > > >
> > > > Thanks for your input.
> > > >
> > > > --Jon
> > > >
> > > > "Kevin Spencer" <kevin@SPAMMERSSUCKtakempis.com> wrote in message
> > > > news:e7PLnRzPDHA.2460@TK2MSFTNGP10.phx.gbl...
> > > > > Well, there is one way that I can think of. On the server side,

you

> > can

> > > > > create a WebRequest, which is an HTTP request for a resource. The
> > > > WebRequest
> > > > > can request the ASP page, which invokes the ASP ISAPI on the web

> > server

> > > to
> > > > > handle that request. The HTML Response from that Request can then

be

> > > > > returned to the browser using Response.Write from the ASP.Net Page
> > > class.
> > > > >
> > > > > HTH,
> > > > >
> > > > > Kevin Spencer
> > > > > Microsoft FrontPage MVP
> > > > > Internet Developer
> > > > > [url]http://www.takempis.com[/url]
> > > > > Big things are made up of
> > > > > lots of Little things.
> > > > >
> > > > > "Jon Sequeira" <jsequeir@twcny.rr.com> wrote in message
> > > > > news:e29AE6yPDHA.2480@tk2msftngp13.phx.gbl...
> > > > > > Thanks.
> > > > > >
> > > > > > I'm looking for a way to do it without Response.Redirect-- I'd

> like

> > > the
> > > > > > redirect to take place on the server, without the browser seeing

> the

> > > new
> > > > > > URL. The intention here is to create a similar effect to an URL
> > > > rewriter,
> > > > > so
> > > > > > that site users and search engines are not aware of the second,

> > target

> > > > > URL,
> > > > > > which contains a number of query string parameters that I don't

> wish

> > > to
> > > > > > expose.
> > > > > >
> > > > > > Any ideas are appreciated.
> > > > > >
> > > > > > --Jon
> > > > > >
> > > > > >
> > > > > > "Kevin Spencer" <kevin@SPAMMERSSUCKtakempis.com> wrote in

message

> > > > > > news:#Cby0pyPDHA.1584@TK2MSFTNGP11.phx.gbl...
> > > > > > > Try Response.Redirect. Server.Transfer works within the

ASP.Net

> > > ISAPI,
> > > > > and
> > > > > > > can never work with ASP pages. Response.Redirect sends a

> redirect

> > > > > request
> > > > > > to
> > > > > > > the browser, which then requests the ASP page appropriately.
> > > > > > >
> > > > > > > HTH,
> > > > > > >
> > > > > > > Kevin Spencer
> > > > > > > Microsoft FrontPage MVP
> > > > > > > Internet Developer
> > > > > > > [url]http://www.takempis.com[/url]
> > > > > > > Big things are made up of
> > > > > > > lots of Little things.
> > > > > > >
> > > > > > > "Jon Sequeira" <jsequeir@twcny.rr.com> wrote in message
> > > > > > > news:u0ESV0xPDHA.1556@TK2MSFTNGP10.phx.gbl...
> > > > > > > > Is there a way to redirect from an ASP.NET page to an ASP

page

> > > > without
> > > > > > > > showing the ASP page's URL in the client's browser?
> > > > > > > >
> > > > > > > > This works perfectly with an HTML page, for example:
> > > > > > > >
> > > > > > > > path = "~/cp/test.htm"
> > > > > > > > Server.Transfer(path, False)
> > > > > > > >
> > > > > > > > But with an .asp extension, the I get an HttpException,

"Error

> > > > > executing
> > > > > > > > child request for ~/cp/test.asp."
> > > > > > > >
> > > > > > > > I suppose the ASP.NET page factory is trying to execute the

> ASP

> > > > page.
> > > > > > > >
> > > > > > > > If anyone has suggestions on another way to accomplish this,

> I'm

> > > > very
> > > > > > > > curious.
> > > > > > > >
> > > > > > > > Thanks.
> > > > > > > >
> > > > > > > > --Jon
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >

> >
> >

>
>