Stephen,

It is a matter of consistency among each of the three values needed for a
mapping.  The URL used for "Browser Path" ends in a  slash, yet the other
two values, "Studio Path" and "Server Path", do not.  Either add a slash to
the end of these two values or remove the slash from the end of the "Browser
Path" value.

Paul Kenney
[EMAIL PROTECTED]


> -----Original Message-----
> From: Stephen Hait [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 23, 2003 11:17 AM
> To: CF-Talk
> Subject: Studio 5 development mappings problem
>
>
> Has anyone encountered this problem and, if so, did you find a
> resolution?
>
> I have W2K Pro running IIS 5 with virtual directories as follows:
> mydir mapped to c:\inetpub\wwwroot\mydir
> mydir2 mapped to c:\inetpub\wwwroot\mydir2
>
> I can browse the contents of both these directories with the URLs:
> http://127.0.0.1/mydir/
> http://127.0.0.1/mydir2/
>
> I've set up two development mappings in Studio 5:
> Studio and server path: c:\intepub\wwwroot\dir
> Browser path: http://127.0.0.1/mydir/
>
> Studio and server path: c:\inetpub\wwwroot\dir2
> Browser path: http://127.0.0.1/mydir2/
>
> Within Studio, I can "browse" mydir no problem but when I try to
> browse files in mydir2 the URL that is trying to be resolved ends
> up as http://127.0.0.1/mydir/2/
>
> The same thing will occur with virtual and physical directories
> named mydir and mydirold; mydirold resolves to
> http://127.0.0.1/mydir/old/
>
> Any light appreciated.
>
> Stephen
> 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4
Subscription: 
http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Your ad could be here. Monies from ads go to support these lists and provide more 
resources for the community. http://www.fusionauthority.com/ads.cfm

                                Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
                                

Reply via email to