Cloaking a large dynamic ASP site

Bit stuck...

[johnser]

Hi
I'm cloaking a site with 4000 products & I'm having some problems with my asp scripts. I want the server to process 2 asp scripts in a row.

I've my main script (index.asp) in the root which redirects based on UA/IP to:

../cloaked/X.html if its a person &
../cloaked/Y.asp if its a SE.

Y.asp is a dynamically-generated template page into which all my product content gets placed (using?ID=2345)

When the main script (index.asp) gets parsed, it correctly serves the Y.asp page to the SE.

Unfortunately none of the asp code now works on Y.asp. (It does when I go to Y.asp directly)

Eg - I visit index.asp?ID=123 and I get redirected to Y.asp but I want Y.asp?ID=123.

How do I get the Win2K server to process my 2 asp scripts in a row?

Thanks all
J

(Mods - Not sure if this is in the right place?)

[DaveN]

Without knowing what cloaking script you are using it's hard to tell what's going south on you.

DaveN

[johnser]

Thx Dave
Not really keen on posting details (or even if its ok to do that?)

Heres how its working:

Theres a GET request to the server.
The server looks at the requested file.
It sees ASP code which it processes.
The ASP code tells it to serve another ASP page which it does.

But it doesn't bother to process the ASP code on the 2nd ASP page...

The 2nd page appears with its <%...%> showing in the browser.....

[MrSpeed]

I had something similar happen with a 404 page. Turned out there was a setting in the site properties the Custom errors tab for the message type that was set wrong.

How does your code look?
Is it a simple response.redirect or a server.transfer?

[johnser]

The main index.asp script is 2 pages long.

The second ASP page is just a very simple ASP page created by Dreamweaver.

Its been suggested to me (not on WW) to combine the 2 scripts into 1 as the server is not going to be able to parse 1 asp script & then another. Any thoughts on that?

Thanks folks
J

[MrSpeed]

I just read your first post again.

You do not want to cloak via a redirect. It sends a 302 header out and it's a surfire way to get in trouble fast.
Besides in your first redirect method /cloaked/Y.asp would be indexed in the search engine..not a different version of /cloaked/X.html

Using one script is a good idea.

<%
if IP/UA = searchengine
response.write something
else
response.write somethingelse
end if

%>

You can also use any other server side method to do this like xmlhttp.

I know I redirect all the time to a second asp page and it parses fine. Sounds like sme strange server setting.