Subweb in ASP.Net?

I'm not realy sure if this is called a "subweb" or not, but here's what I
want to do:

I have a website, smccabe.net

The pages on this site are accessed by the form
http://smccabe.net/somepage.aspx
What I would like to do is create a page accessed with the form:

http://somepage.smccabe.net
How do you do this with ASP.Net?

Thanks!
--SeldenYes, that form of addressing is called a subweb and requires the use of host
headers. Its an IIS configuration.

<%= Clinton Gallagher
NET csgallagher AT metromilwaukee.com
URL http://clintongallagher.metromilwaukee.com/
MAP http://wikimapia.org/#y=43038073&x=...38&z=17&l=0&m=h
"Selden" <seldenm@.msn.comwrote in message
news:_663h.18156$gU6.7744@.tornado.socal.rr.com...

Quote:

Originally Posted by

I'm not realy sure if this is called a "subweb" or not, but here's what I
want to do:
>
I have a website, smccabe.net
>
The pages on this site are accessed by the form
http://smccabe.net/somepage.aspx
>
What I would like to do is create a page accessed with the form:
>
http://somepage.smccabe.net
>
How do you do this with ASP.Net?
>
Thanks!
--Selden
>
>

Selden,
Actually, it's not really a subweb. A "subweb" would be
http://smccabe.net/somepage/ in IIS terminology. Usually when IIS refers to
a subweb it is referring to a logical entity packed as a FrontPage subweb,
which is basically a directory that has been compartmentalized for use by
the FrontPage Server Extensions and FrontPage publishing.

What you are referring to is a subdomain. You would first have to setup
the DNS settings in order to handle the subdomain so it points somewhere.
It's possible that you could have the server automatically point the entry
so that it exists within your site, but at a directory different from the
root. In orther words http://somepage.smccabe.net would map to
http://smccabe.net/somepage/ In some scenarious this becomes unstable
because you would have subdirectories of your root web being seen by the
application possibly as the root level of the site.

Basically, this is a server setup that you wouldn't do in ASP.Net.
Has to be configured through DNS and IIS itself.

--
Hope this helps,
Mark Fitzpatrick
Former Microsoft FrontPage MVP 199?-2006

"Selden" <seldenm@.msn.comwrote in message
news:_663h.18156$gU6.7744@.tornado.socal.rr.com...

Quote:

Originally Posted by

I'm not realy sure if this is called a "subweb" or not, but here's what I
want to do:
>
I have a website, smccabe.net
>
The pages on this site are accessed by the form
http://smccabe.net/somepage.aspx
>
What I would like to do is create a page accessed with the form:
>
http://somepage.smccabe.net
>
How do you do this with ASP.Net?
>
Thanks!
--Selden
>
>

Thanks, you've cleared it up perfectly!

"Mark Fitzpatrick" <markfitz@.fitzme.comwrote in message
news:u4y8q$FAHHA.204@.TK2MSFTNGP04.phx.gbl...

Quote:

Originally Posted by

Selden,
Actually, it's not really a subweb. A "subweb" would be
http://smccabe.net/somepage/ in IIS terminology. Usually when IIS refers
to a subweb it is referring to a logical entity packed as a FrontPage
subweb, which is basically a directory that has been compartmentalized for
use by the FrontPage Server Extensions and FrontPage publishing.
>
What you are referring to is a subdomain. You would first have to setup
the DNS settings in order to handle the subdomain so it points somewhere.
It's possible that you could have the server automatically point the entry
so that it exists within your site, but at a directory different from the
root. In orther words http://somepage.smccabe.net would map to
http://smccabe.net/somepage/ In some scenarious this becomes unstable
because you would have subdirectories of your root web being seen by the
application possibly as the root level of the site.
>
Basically, this is a server setup that you wouldn't do in ASP.Net.
Has to be configured through DNS and IIS itself.
>
>
--
Hope this helps,
Mark Fitzpatrick
Former Microsoft FrontPage MVP 199?-2006
>
>
>
"Selden" <seldenm@.msn.comwrote in message
news:_663h.18156$gU6.7744@.tornado.socal.rr.com...

Quote:

Originally Posted by

>I'm not realy sure if this is called a "subweb" or not, but here's what I
>want to do:
>>
>I have a website, smccabe.net
>>
>The pages on this site are accessed by the form
>http://smccabe.net/somepage.aspx
>>
>What I would like to do is create a page accessed with the form:
>>
>http://somepage.smccabe.net
>>
>How do you do this with ASP.Net?
>>
>Thanks!
> --Selden
>>
>>

>
>

Suggestion Regarding Securing the ASP.NET Web Page......

Hi Everybody,
I have problem regarding security of the page. I want that the every asp.net
web page is accessed via application. If a user directly access the page via
writing the address of the page in the address bar. Then It should be
blocked to access the page.
I have two options in my mind.
1. Using Query String Parameters
2. Using Session Object
But I got the following problem with these techniques.
WIth Query String the problem is that if the user access the page via
application then the query string parameters are shown in the address bar so
there he can used these parameters in the direct access, which i did not
want.
With Session Object, If the user login from the application then its session
is created. so now he can write the direct address in the address bar to
access the page directly which i dont want.
Actully My application is frames base application.
There are threee frames vertically
1) Header
2) Body ( Body Portion contains the two horizontal frames )
2.1) Menu
2.2) Content
3) Footer
In the menu area user selects the menu and against that menu the page is
loaded in the content portion.
So please help me how can i block user to access the page directly.
Regards,
Muhammad Jamil NawazThe Request object will have an HttpRequest.UrlReferrer Property. If this
property does not have a value then it means that the user has typed the
URI. This is not a foolproff method though but can still keep the average
user.
Regards,
Trevor Benedict R
MCSD
"Muhammad Jamil Nawaz" <jamfiza12@.hotmail.com> wrote in message
news:%23$JElX80FHA.2752@.TK2MSFTNGP12.phx.gbl...
> Hi Everybody,
> I have problem regarding security of the page. I want that the every
> asp.net
> web page is accessed via application. If a user directly access the page
> via
> writing the address of the page in the address bar. Then It should be
> blocked to access the page.
> I have two options in my mind.
> 1. Using Query String Parameters
> 2. Using Session Object
> But I got the following problem with these techniques.
> WIth Query String the problem is that if the user access the page via
> application then the query string parameters are shown in the address bar
> so
> there he can used these parameters in the direct access, which i did not
> want.
> With Session Object, If the user login from the application then its
> session
> is created. so now he can write the direct address in the address bar to
> access the page directly which i dont want.
> Actully My application is frames base application.
> There are threee frames vertically
> 1) Header
> 2) Body ( Body Portion contains the two horizontal frames )
> 2.1) Menu
> 2.2) Content
> 3) Footer
> In the menu area user selects the menu and against that menu the page is
> loaded in the content portion.
> So please help me how can i block user to access the page directly.
> Regards,
> Muhammad Jamil Nawaz
>
Use Session.
Use the sessionstate as "auto" mode (not cookieless = false) to also
take care of scenarios where cookies may be disabled (a large section
of corporates disable cookies).
Cheers,
Gaurav Vaish
http://mastergaurav.org
--