Hi,

Don't know if anyone can help but here goes. I have a dot net app which
is running very nicely until you hit the final checkout button or the
login button both of which are at another addy(which is where the
problem lies I think). Then the config file throws a wobbly and it all
goes pear shaped. The config file has this bit in it

<!--<location path="CheckOut.aspx">-->
<location path="CheckOut.aspx">
<system.web>
<authorization>
<deny users="?" />
</authorization>
</system.web>
</location>

However it really needs (I think!) to say :
<location path="https://name of
server/firstlineinteractive/nameoffile.aspx"> BUT
When I do that it throws a wobbly cause it wants a virtual addy and not
the https: mularkey. Now if the client wanted to buy their own
certificate I believe I'd not have a problem, but they don't! So I need
to make this work. Any ideas???

This all works locally as the location path merely points at
"Secure/Checkout.aspx" and the folder is in the same area etc etc, but
of course on the server its on another actual server! Tearing my hair
out looking for a way to do this, it may be pretty obvious and I could
be looking for something more complex but .........

All ideas welcome,

Sue.
(who's going grey for Easter!)

----------------------------------------------
Archives:<http://www.listsearch.com/DreamweaverTalk.lasso>
Administrator:<mailto:dreamweaver-admin@blueworld.com>
Unsubscribe:<mailto:dreamweaver-request@blueworld.com>
with the body containing: unsubscribe dreamweaver