PHP "Virtual Host" Site error Using Dreamweaver

I created a virtual host on my local machine. I am using Apache, php5, and mysql 5. I moved my "wordpress files and folders" into the root folder for my site. My htdocs looks like this;
<VirtualHost *:80>
  ServerName localhost
  DocumentRoot "C:/Program Files/Apache Group/Apache/htdocs"
</VirtualHost>
<VirtualHost *:80>
  ServerName myvirtualrootfolder.com
  DocumentRoot "C:/Program Files/Apache Group/Apache/htdocs/myvirtualrootfolder"
  <Directory "C:/Program Files/Apache Group/Apache/htdocs/myvirtualrootfolder">
    Options FollowSymLinks Indexes
    Allow from all
    Order allow,deny
    AllowOverride All
  </Directory>
</VirtualHost>
I followed the dynamic dreamweaver setup. Next I see, "This page may have dynamically-related files that can only be discovered by the server. When I click "Discover", I'm told "my site definition isn't correct." Can anyone help me please?

>Sorry. I just never get any help here
Really? Doesn't look that way to me:
http://forums.adobe.com/people/buffbill?view=overview
Other than a post from last week, and those you just posted within the past few hours....it looks like you are getting replies.  I'm just sayin.

Similar Messages

  • PHP "Virtual Host" 3/4% Correct, but Still error?

    PHP "Virtual Host" Site error Using Dreamweaver
    I created a virtual host on my local machine. I am using Apache, php5, and mysql 5. I moved my "wordpress files and
    folders" into the root folder for my site. My htdocs looks like this;
    <VirtualHost *:80>
      ServerName localhost
      DocumentRoot "C:/Program Files/Apache Group/Apache/htdocs"
    </VirtualHost>
    <VirtualHost *:80>
      ServerName myvirtualrootfolder.com
      DocumentRoot "C:/Program Files/Apache Group/Apache/htdocs/myvirtualrootfolder"
      <Directory "C:/Program Files/Apache Group/Apache/htdocs/myvirtualrootfolder">
        Options FollowSymLinks Indexes
        Allow from all
        Order allow,deny
        AllowOverride All
      </Directory>
    </VirtualHost>
    I followed the dynamic dreamweaver setup. Next I see, "This page may have dynamically-related files that can only be
    discovered by the server. When I click "Discover", I'm told "my site definition isn't correct." Can anyone help me
    please?

    >Sorry. I just never get any help here
    Really? Doesn't look that way to me:
    http://forums.adobe.com/people/buffbill?view=overview
    Other than a post from last week, and those you just posted within the past few hours....it looks like you are getting replies.  I'm just sayin.

  • PHP virtual host specific settings

    Hi,
    is possible to have some php settings defined differently fo
    virtual hosts ? Our global php configuration has safe mode
    enabled by default, but some virtual hosts need safe mode
    to be off.

    >Sorry. I just never get any help here
    Really? Doesn't look that way to me:
    http://forums.adobe.com/people/buffbill?view=overview
    Other than a post from last week, and those you just posted within the past few hours....it looks like you are getting replies.  I'm just sayin.

  • Swf site uploading using dreamweaver

    I made a site using indesign and saved it as .swf but i don't know how to upload this. It doesnt open in dreamweaver and i inserted and tried different things,
    but it doesnt work and i don't know how.
    Does anyone know how to upload this kind of document in dreamweaver

    It doesnt open in dreamweaver
    Right - DW doesn't edit SWF files.  Here's what to do:
    In DW, create a site by defining a local folder that will contain the SWF file
    Then define a remote location for that site by entering the host name, the user ID and password, and the name of the root directory of the remote site (usually public_html, or httpd, or www)
    Using the connect button on the Files panel, make an FTP connection with this remote site, and drag and drop the SWF file onto the folder where you want it to be accessed
    That should do what you want.

  • The essential guide to DW cs4... by D. Powers: when from wamp to xampp+virtual host and having problems :(

    Following the book in chapter 2 I think Ivé followed everything correctly, but have encluded all the things I've edited below.
    I was using wamp with no problems but after trying to set up a virtual host and now using xampp im abit lost its probabsomething stupid but I can find the prob.
    (This post is abit long and dragged out so I used some colour to try ease the reading..)
    When I try to view a dynamic page in live view or in firefox I get the following error:
    **when using:
    <VirtualHost *:80>
    DocumentRoot c:/xampp/htdocs
    ServerName localhost
    </VirtualHost>
    result:
    Access forbidden!
    You don't have permission to access the requested object.     It is either read-protected or not readable by the server.
    If you think this is a server error, please contact the webmaster.
    Error 403
    thegoodlife
    2009/10/13 12:47:48 PM
    Apache/2.2.12 (Win32) DAV/2 mod_ssl/2.2.12 OpenSSL/0.9.8k mod_autoindex_color PHP/5.3.0 mod_perl/2.0.4 Perl/v5.10.0
    *when using:
    <VirtualHost *:80>
    DocumentRoot c:/htdocs
    ServerName localhost
    </VirtualHost>
    result:
    Object not found!
    The requested URL was not found on this server.          If you entered the URL manually please check your     spelling and try again.
    If you think this is a server error, please contact the webmaster.
    Error 404
    thegoodlife
    2009/10/13 12:32:58 PM
    Apache/2.2.12 (Win32) DAV/2 mod_ssl/2.2.12 OpenSSL/0.9.8k mod_autoindex_color PHP/5.3.0 mod_perl/2.0.4 Perl/v5.10.0
    This is what I've done, blue indicating where I have or was meant to edit, red being the relivant context. (hope it helps )
    1. Created a new folder called htdocs (C:\htdocs)
    2. Changed the pathname to:
    # DocumentRoot: The directory out of which you will serve your
    # documents. By default, all requests are taken from this directory, but
    # symbolic links and aliases may be used to point to other locations.
    DocumentRoot "C:/htdocs"
    and
    # This should be changed to whatever you set DocumentRoot to.
    <Directory "C:/htdocs">
    3. Created vhosts folder; with a sub-folder called thegoodlife (C:\vhosts)
    4. entered new vhost:
    # Additionally, comments (such as these) may be inserted on individual
    # lines or following the machine name denoted by a '#' symbol.
    # For example:
    #      102.54.94.97     rhino.acme.com          # source server
    #       38.25.63.10     x.acme.com              # x client host
    127.0.0.1 localhost
    127.0.0.1 dwcs4
    127.0.0.1 thegoodlife
    127.0.0.1 bin.errorprotector.com ## added by CiD
    5.It says uncomment the command by removing the #, (Supplemental configuation.), but this is the origional file; already uncommented?
    # Real-time info on requests and configuration
    Include "conf/extra/httpd-info.conf"
    # Virtual hosts
    Include "conf/extra/httpd-vhosts.conf"
    # Distributed authoring and versioning (WebDAV)
    Include "conf/extra/httpd-dav.conf"
    6.Set the permissions and changed the code as instructed, unsing (c:/xampp/htdocs) as advised.
    # You may use the command line option '-S' to verify your virtual host
    # configuration.
    <Directory C:/vhosts>
      Order Deny,Allow
      Allow from all
    </Directory>
    # Use name-based virtual hosting.
    ##NameVirtualHost *:80
    # VirtualHost example:
    # Almost any Apache directive may go into a VirtualHost container.
    # The first VirtualHost section is used for all requests that do not
    # match a ServerName or ServerAlias in any <VirtualHost> block.
    <VirtualHost *:80>
    DocumentRoot c:/xampp/htdocs
    ServerName localhost
    </VirtualHost>
    <VirtualHost *:80>
    DocumentRoot c:/vhosts/dwcs4
    ServerName dwcs4
    </VirtualHost>
    <VirtualHost *:80>
    DocumentRoot c:/vhosts/thegoodlife
    ServerName thegoodlife
    </VirtualHost>
    Then creating the site definition:
    local root forlder: C:\htdocs\thegoodlife\
    testing server folder: C:\vhosts\thegoodlife\
    URL prefix: http://thegoodlife/
    hope i've covered all area's where I could have gone wrong

    Just one more thing - the description of what i did while first Kernel appeared:
    Happened 2 days ago. Wasn't turning it off for like a day, only sleep mode by closing it. Worked fine all day, wasn't doing anything, except for checking mail 2-3 times and having windows 7 virtual machine opened but doing nothing, everything was going fine. Then closed it without turning off.
    Opened 3-4 hours later, everything was working fine for 30 minutes of checking mail, then Kernel appeared. After that pretty much everything i did is described in part 1-5.
    Note: all the time MBP was connected to internet via wifi, so updates to both MBP and virtual machine of all programs were possible.
    I only shared downloads and desktop folders, so windows couldn't have access to system folder of Mac Os.
    Hope this might help...Thanks again.

  • Virtual Hosts - I'm lost!

    I've been pulling my hair out trying to figure out how to get MySQL, phpMyAdmin and virtual hosts set up on my MacBook Pro. I finally paid a computer science student $100 to do it for me, and he botched it, so I'm now going back to square one.
    My websites are located in /Users/username/sites/. I've modified the httpd.conf, hosts and NetInfo files, and I can now preview the home page of ONE of my virtual host sites. The problem is that I see the page whether I type http://localhost/, http://Geobop/, http://GW/ or http://GS/ into my browser. It should preview only at http://Geobop/.
    I rediscovered the article Enabling Virtual Hosts on MacOS X at http://www.evolt.org/article/EnablingVirtual_Hosts_on_MacOSX/18/13138/
    and added a script to my httpd.conf file, as follows:
    # Leave this one alone - it makes sure that localhost works.
    <VirtualHost 127.0.0.1>
    DocumentRoot /Library/WebServer/Documents
    ServerName localhost
    </VirtualHost>
    #<VirtualHost 127.0.0.1:80>
    # ServerName geobop
    # ServerAdmin [email protected]
    # DocumentRoot /Users/MYNAME/Sites/Geobop
    #</VirtualHost>
    If I understand correctly, this is supposed to make http://localhost/ display something unique, rather than a local website. However, all the URL's I cited above still display the same thing...but this time around they display blank pages with columns of numerals along the left margin.
    In an earlier experiment, I deleted all my virtual hosts from httpd.conf. Then all these URL's displayed the following:
    Index of /
    Name Last modified Size Description
    [DIR] Parent Directory 13-Mar-2007 15:49 -
    [ ] index.php 06-Oct-2006 15:36 1k
    [ ] php5.fcgi 06-Oct-2006 18:18 1k
    [ ] phpMyAdmin-2.9.0.2.tar 06-Oct-2006 17:44 11.4M
    [ ] phpinfo.php 06-Oct-2006 15:20 1k
    [ ] phpinfo.php5 06-Oct-2006 18:20 1k
    Apache/1.3.33 Server at localhost Port 80
    Can someone tell me what's going on and how to fix it? If I can get Apache and my virtual hosts squared away, then I'm going to try to get MySQL and phpMyAdmin back up and running.
    Thanks.

    I don't know much about it, but I do have two comments since it does not sound like a virtual hosts problem.
    1) Netinfo Machines will not work by default. You will need to configure lookupd to give Netinfo priority over DNS:
    lookupd -configuration
    The default configuration will be:
    LookupOrder: Cache FF DNS NI DS
    configname: Host Configuration
    What you need to do is configure lookupd to give NI priority over DNS. Here is how it should look:
    LookupOrder: Cache NI FF DNS DS
    To do this, use commands like this, you will need to have root access enabled:
    su
    lookupd -configuration
    cd /etc
    sudo mkdir lookupd
    cd lookupd
    echo LookupOrder Cache NI FF DNS DS > hosts
    reboot
    lookupd -configuration
    After rebooting, your lookupd order should put NI in front of DNS. Now you can make entries in the "machines" column to your local domains.
    2) MySQL is not installed, however a socket is configured so yeah it's a little confusing. You have to go to the website http://dev.mysql.com/downloads/mysql/5.0.html and scroll down to OSX. Just ignore the pesky questionnaire screen before the download page.

  • Virtual hosts in apache defaults to first host

    On my MacMini I have set up apache to use virtual hosts I and use a mounted USB drive to host the sites (in my case /Volumes/Work1/www as root). I have configured 3 sites and switch on the subdomain (in my case and in order in the virtual hosts file: hbc1.helsted.net, consulting.helsted.net, store.helsted.net).
    On the MacMini I have inserted the urls in the hosts file to point at localhost for two of the entries and all work beautifully on the MacMini for those two. Anywhere else (and from the MacMini on the one not in the hosts file) the system defaults to the first entry in the virtual hosts config file (as the documentation says it will if the url is not recognized) which is displayed in the browser and which has entries in the log file.
    After some time the server occasionally refuses to serve the pages and I get a 403 error (access denied). Again not on the MacMini with the hosts file entries. Looking at the error log from apache in that case it appear that it has got the full url served as it is in the log file.
    Restarting the web share removes the 403 error (until next time).
    Any hints on how to to resolve my two issues?

    Thanks for the reply, my vhosts config file contains the following (note that the viewer in the forum browser removes the initial #es on the comment lines):
    # Virtual Hosts
    # If you want to maintain multiple domains/hostnames on your
    # machine you can setup VirtualHost containers for them. Most configurations
    # use only name-based virtual hosts so the server doesn't need to worry about
    # IP addresses. This is indicated by the asterisks in the directives below.
    # Please see the documentation at
    # <URL:<a class="jive-link-external-small" href="http://">http://httpd.apache.org/docs/2.2/vhosts/>
    # for further details before you try to setup virtual hosts.
    # You may use the command line option '-S' to verify your virtual host
    # configuration.
    # Use name-based virtual hosting.
    NameVirtualHost *:80
    # VirtualHost example:
    # Almost any Apache directive may go into a VirtualHost container.
    # The first VirtualHost section is used for all requests that do not
    # match a ServerName or ServerAlias in any <VirtualHost> block.
    <VirtualHost *:80>
    ServerAdmin [email protected]
    DocumentRoot "/Volumes/Work1/www/hbc1"
    ServerName hbc1.helsted.net
    ErrorLog "/private/var/log/apache2/hbc1.helsted.net-error_log"
    CustomLog "/private/var/log/apache2/hbc1.helsted.net-access_log" common
    </VirtualHost>
    <VirtualHost *:80>
    ServerAdmin [email protected]
    DocumentRoot "/Volumes/Work1/www/consulting"
    ServerName consulting.helsted.net
    ErrorLog "/private/var/log/apache2/consulting.helsted.net-error_log"
    CustomLog "/private/var/log/apache2/consulting.helsted.net-access_log" common
    </VirtualHost>
    <VirtualHost *:80>
    ServerAdmin [email protected]
    DocumentRoot "/Volumes/Work1/www/store"
    ServerName store.helsted.net
    ErrorLog "/private/var/log/apache2/store.helsted.net-error_log"
    CustomLog "/private/var/log/apache2/store.helsted.net-access_log" common
    </VirtualHost>
    <Directory /Volumes/Work1/www>
    Options Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
    AllowOverride All
    Order allow,deny
    Allow from all
    </Directory>
    Message was edited by: skhelsted

  • Virtual Hosts vs Localhost

    OK, I'm on about step #13 of Apple's virtual hosts enabling obstacle course, and I'm still confused. I've modified the httpd.conf, hosts and NetInfo files, and I can now preview the home page of ONE of my virtual host sites. The problem is that I see the page whether I type in http://localhost/, http://Geobop/, http://GW/ or http://GS/. It should preview only at http://Geobop/.
    I rediscovered the article Enabling Virtual Hosts on MacOS X at http://www.evolt.org/article/EnablingVirtual_Hosts_on_MacOSX/18/13138/
    and added a script to my httpd.conf file, as follows:
    # Leave this one alone - it makes sure that localhost works.
    <VirtualHost 127.0.0.1>
    DocumentRoot /Library/WebServer/Documents
    ServerName localhost
    </VirtualHost>
    #<VirtualHost 127.0.0.1:80>
    # ServerName geobop
    # ServerAdmin [email protected]
    # DocumentRoot /Users/MYNAME/Sites/Geobop
    #</VirtualHost>
    If I understand correctly, this is supposed to make http://localhost/ display something unique, rather than a local website. However, all the URL's I cited above still display the same thing...but this time around they display blank pages with columns of numerals along the left margin.
    In an earlier experiment, I deleted all my virtual hosts from httpd.conf. Then all these URL's displayed the following:
    Index of /
    Name Last modified Size Description
    [DIR] Parent Directory 13-Mar-2007 15:49 -
    [ ] index.php 06-Oct-2006 15:36 1k
    [ ] php5.fcgi 06-Oct-2006 18:18 1k
    [ ] phpMyAdmin-2.9.0.2.tar 06-Oct-2006 17:44 11.4M
    [ ] phpinfo.php 06-Oct-2006 15:20 1k
    [ ] phpinfo.php5 06-Oct-2006 18:20 1k
    Apache/1.3.33 Server at localhost Port 80
    Can someone tell me what's going on and how to fix it. This process was three times easier on my PC, though I hate Microsoft.
    Thanks.

    Thanks for your explainations but it keeps frustrating me. I'll try to give an exact overview to my settings and my tries to implement your suggestions:
    Computer name: MacBook Pro
    Host: server.local
    Wi-Fi: 192.168.178.100 (static, as I said no DHCP)
    DNS-Settings:
    Forwarding Servers: 192.168.178.100
    Perform lookups for only some clients: "The server itself" and "Clients on the local network"
    Host name: server.local
    IP address: 192.168.178.100
    (no aliases)
    automatically created after setting this host name:
         Primary zone: server.local
         Machine: zone: server.local, host name: server.local, IP address: 192.168.178.100
         Nameserver: zone: server.local, Name-server: server.local
    Now I create a new host:
    Host name: thenewwebsite.site
    IP address: 192.168.178.100
    (no aliases)
    automatically created after setting this host name:
         Primary zone: thenewwebsite.site
         Machine: zone: thenewwebsite.site, host name: thenewwebsite.site, IP address: 192.168.178.100
         Nameserver: zone: thenewwebsite.site, Name-server: thenewwebsite.site
    Now going to "Web" service:
    hit the [+] button
    domain-name: thenewwebsite.site
    --> and it gives me the red bullet again saying it could not resolve this and trying to load "thenewwebsite.site" from the browser consequently fails.
    I also tried to set the machine-zone and the nameserver-zone for the thenewwebsite.site host to server.local - didn't changed anything, loading "thenewwebsite.site" fails.
    Designed in California, designed to make ist easier ??? huu ???

  • Virtual Hosts in Apache HTTP Server

    How to configure virtual hosts in Apache HTTP Server httpd.conf file.
    If I want to access my server with some other name(alias), how can I do this ?
    Suggestions in this matter would be highly helpful.
    Thanks
    Vidhyut Arora

    Following is a note explaining how to setup
    Virtual hosts.
    Hope this helps
    Ranga
    Note:70647.1
    Subject: Apache Server Virtual Hosting
    Last Revision Date: 07-JUN-2001
    PURPOSE
    This document discusses considerations for setting up virtual hosts on an
    Apache machine, to include how to get the hostname working and how to
    configure Apache.
    SCOPE & APPLICATION
    The information in this document is intended for those who manage multiple sites
    using an Apache machine.
    REFERENCES
    First published in Apache Week issue 31 (6th September 1996)
    Last update 20th September 1998
    Using Virtual Hosts
    Virtual Hosts let you run multiple independent Web sites on a single host with
    a single Apache setup.
    One of the most important facilities in Apache is its ability to run virtual
    hosts. This is now the essential way to run multiple Web services - each with
    different host names and URLs - that appear to be completely separate sites.
    This is widely used by ISPs, hosting sites and content providers who need to
    manage multiple sites but do not want to buy a new machine for each one.
    Picking an IP address
    There are two types of virtual hosts: IP-based and non-IP-based. The former is
    where each virtual host has its own IP address. You must have a new IP address
    for each virtual host you want to set up, either from your existing allocation
    or by obtaining more from your service provider. When you have extra IP
    addresses, you tell your machine to handle them. On some operating systems, you
    can give a single ethernet interface multiple addresses (typically with an
    fconfig alias command). On other systems, you must have a different
    physical interface for each IP address (typically by buying extra ethernet
    cards).
    IP addresses are a resource that costs money and are increasingly difficult to
    get, so modern browsers can now also use 'non-IP' virtual hosts. This
    lets you use the same IP address for multiple host names. When the server
    receives an incoming Web connection, it does not know the hostname that was used
    in the URL. However, the new HTTP/1.1 specification adds a facility where the
    browser must tell the server the hostname it is using, on the Host: header. If
    an older browser connects to a non-IP virtual host, it does not send the Host:
    header, so the server must respond with a list of possible virtual
    hosts. Apache provides some help for configuring a site for both old and new
    browsers.
    Picking a Hostname and Updating the DNS
    Having selected an IP address, the next stage is to update the DNS so that
    browsers can convert the hostname into the right address. The DNS is the system
    that every machine connected to the internet uses to find the IP address of host
    names. If your hostname is not in the DNS, no one can connect to
    your server (except by the unfriendly IP address).
    If the virtual hostname you are going to use is under your existing domain,
    you can just add the record into your own DNS server. If the virtual hostname
    is in someone else's domain, you must get them to add it to their DNS
    server files. In some cases, you want to use a domain not yet used on the
    internet, in which case you must apply for the domain name from the
    InterNIC and set up the primary and secondary DNS servers for it, before adding
    the entry for your virtual host.
    In any of these cases, the entry you need to add to the DNS is an address record
    (an A record) pointing to the appropriate IP address. For example, say you want
    the domain www.my-dom.com to access your host with IP address 10.1.2.3: you
    must add the following line to the DNS zone file for my-dom.com:
    www A 10.1.2.3
    Now, users can enter http://www.my-dom.com/ as a URL in their browsers and get
    to your Web server. However, it will return the same information as if the
    machine's original hostname had been used. So, the final stage is to tell Apache
    how to respond differently to the different addresses.
    How Apache Handles Virtual Hosts
    Configuring Apache for virtual hosts is a two-stage process. First, it needs
    to be told which IP addresses (and ports) to listen to for incoming Web
    connections. By default, Apache listens to port 80 on all IP addresses of the
    local machine, and this is often sufficient. If you have a more complex
    requirement, such as listening on various port numbers, or only to specific IP
    addresses, then the BindAddress or Listen directives can be used.
    Second, having accepted an incoming Web connection, the server must be
    configured to handle the request differently, depending on what virtual host it
    was addressed to. This usually involves configuring Apache to use a different
    DocumentRoot.
    Telling Apache Which Addresses to Listen To
    If you are happy for Apache to listen to all local IP addresses on the port
    specified by the Port directive, you can skip this section. However, there are
    some cases where you want to use the directives explained here:
    - If you have many IP addresses on the machine but only want to run a Web
    server on some of them
    - If one or more of your virtual hosts is on a different port
    - If you want to run multiple copies of the Apache server serving different virtual
    hosts
    There are two ways of telling Apache what addresses and ports to listen to:
    - Use the BindAddress directive to specify a single address or port
    - Use the Listen directive to any number of specific addresses or ports
    For example, if you run your main server on IP address 10.1.2.3 port 80, and a
    virtual host on IP 10.1.2.4 port 8000, you would use:
    Listen 10.1.2.3:80
    Listen 10.1.2.4:8000
    Listen and BindAddress are documented on the Apache site.
    Configuring the Virtual Hosts
    Having gotten Apache to listen to the appropriate IP addresses and ports, the
    final stage is to configure the server to behave differently for requests on
    each of the different addresses. This is done using <VirtualHost> sections in
    the configuration files, normally in httpd.conf.
    A typical (but minimal) virtual host configuration looks like this:
    <VirtualHost 10.1.2.3>
    DocumentRoot /www/vhost1
    ServerName www.my-dom.com
    </VirtualHost>
    This should be placed in the httpd.conf file. You replace the text
    10.1.2.3 with one of your virtual host IP addresses. If you want to specify a
    port as well, follow the IP address with a colon and the port number
    (example: 10.1.2.4:8000). If omitted, the port defaults to 80.
    If no <VirtualHost> sections are given in the configuration files, Apache
    treats requests from the different addresses and ports identically. In terms of
    setting up virtual hosts, we call the default behavior the main server
    configuration. Unless overridden by <VirtualHost> sections, the main server
    behaviour is inherited by all the virtual hosts. When configuring virtual
    hosts, you must decide what changes to make in each of the virtual
    host configurations.
    Any directives inside a <VirtualHost> section apply to just that virtual host.
    The directives either override the configuration give in the main server, or
    supplement it, depending on the directive. For example, the DocumentRoot
    directive in a <VirtualHost> section overrides the main server's DocumentRoot,
    while AddType supplements the main server's mime types.
    Now, when a request arrives, Apache uses the IP address and port it arrived on
    to find a matching virtual host configuration. If no virtual host matches the
    address and port, it is handled by the main server configuration. If it does
    match a virtual host address, Apache uses the configuration of that virtual
    server to handle the request.
    For the example above, the server configuration used is the same as the
    main server, except that the DocumentRoot is /www/vhost1, and the
    ServerName is www.my-dom.com. Directives commonly set in <VirtualHost>
    sections are DocumentRoot, ServerName, ErrorLog and TransferLog. Directives
    that deal with handling requests and resources are valid inside <VirtualHost>
    sections. However, some directives are not valid inside <VirtualHost> sections,
    including BindAddress, StartSevers, Listen, Group and User.
    You can have as many <VirtualHost> sections as you want. You can
    leave one or more of your virtual hosts being handled by the main server, or
    have a <VirtualHost> for every available address and port, and leave the main
    server with no requests to handle.
    VirtualHost sections for non-IP Virtual Hosts
    Non-IP virtual hosts are configured in a very similar way. The IP address that
    the requests arrive on is given in the <VirtualHost> directive, and the
    host name is put in the ServerName directive. The difference is that there
    (usually) is more than one <VirtualHost> section handling the same IP address.
    For Apache to know whether a request arriving on a particular IP
    address is supposed to be a name-based requests, the NameVirtualHost directive
    addresses for name-based requests. A virtual host can handle more than one
    non-IP hostname by using the ServerAlias directive, in addition to the
    ServerName.
    null

  • Who really uses Dreamweaver?

    I have been a long time user of Dreamweaver and I am really pleased with CS4 and the new abilities to keep track of linked files etc.
    However, I have noticed that almost none of the other sites I visit seem to be built using Dreamweaver. I frequently scour other sites for design and technical ideas but very very rarely see evidence of Dreamweaver having been used - eg. I don't think I have ever seen a commercial site that uses Dreamweaver templates. I understand that a lot of sites these days are based on content management systems, but among the static sites that are out there I almost never find sites that appear to have been designed using dreamweaver.
    So my question is, does anyone really use Dreamweaver for commercial , production sites and what features (eg. Templates, Spry, ICE) do they use?

    richardhellyer wrote:
    So my question is, does anyone really use Dreamweaver for commercial , production sites
    I do, but I almost never use any of its extended features. I edit my stylesheets in TopStyle when I'm on my PC, because it's easier to navigate and more intuitive than DW's CSS stuff and I clean up messy code in Smultron (Mac) or Textpad (PC), if and when DW's search features are too slow or it refuses to acknowledge some stuff and conks out. The Spry stuff is okay, but I have not yet found an excuse to use it and a lot of other JavaScript code can be found on the web, so one is not too dependent on Spry and the Behaviors panel. The rest of the time DW is just fine and compared to other HTML editors it's surely the most complete package. The only real problem I have, is its rigid approach to dealing with dynamic content. This includes the aforementioned Behaviors panel and naturally, the program being unable to deal even with common CMS systems beyond the likewise rigid Databases panel, is not really helping when working on nested PHP documents and such. You know, empty data regions that are completely meaningless when empty and similar things... It really needs to have a way to connect woith PHP/ CFM/ JSP(A)/ ASP that extends LiveView.
    Mylenium

  • SSL virtual host with external hardware accelerator/LBR

    Hi all,
    We have an existing non-ssl site configured - http://abc.company1.com
    We wish to add a new https site - https://xyz.company2.com - and terminate SSL at our hardware load balancer. But obviously keep our existing http site available.
    However, we can't seem to get this to work. We added a new site to the Web Cache, registered it with sso, updated httpd.conf and iasconfig.xml with the new virtual host and ran ptlconfig.
    Has anyone successfuly implemented a similar configuration?
    Is it possible to have a mixture of http and https virtual hosts with SSL termination at the LBR?
    Thanks in advance,
    Andy

    Yeah, in the app server admin guide for SSL configuration:
    17.3.5 Enabling SSL in Virtual Hosts
    You can use virtual hosts to deploy multiple Web sites on a single Oracle HTTP Server (for example, to make an application available over the HTTP protocol and the HTTPS protocol).
    The Oracle Application Server Single Sign-On Administrator's Guide, section titled "Configuring mod_osso with Virtual Hosts" contains instructions on configuring an SSL virtual host to be protected by mod_osso. You cannot use name-based virtual hosting. You must use IP-based or port-based virtual hosting.
    //This may be your problem - granted no symptoms were provided.

  • Virtual host doesn't work in NW CE 7.1 EHP 1 SP07

    Hi all,
    I've created a virtual host in nwa using "Java HTTP Provider Configuration: Virtual Hosts"
    (f.e. virtual host named "we2")
    But I can't access to this using http://we2:50000. I don't know why.
    DNS is up to date.
    many thanks
    Sven
    Edited by: Sven Rickelt on Sep 20, 2011 3:16 PM

    Hi,
    Have you done configuration as per below link:
    http://help.sap.com/SAPHELP_nwpi711/helpdata/en/f5/875342d8a7be30e10000000a155106/content.htm
    http://help.sap.com/saphelp_nwpi71/helpdata/en/44/9a891684d360d6e10000000a114a6b/content.htm
    Thanks
    Sunny

  • Forms Virtual Hosts?

    Hi,
    Is it possible to use forms with virtual hosts? I have configured a virtual host in apache conf but the new virtual host is never used in forms.
    original host
    www.oldhost.com
    my new virtual host
    www.newhost.com
    when I write in url www.newhost.com/forms/frmservlet?config=xxx i am always redirected to www.oldhost.com/forms/frmservlet?config=xxx
    Thanks
    Joao Oliveira

    Any can help? Forms team?

  • Dreamweaver CS5 with PHP, not getting it to work with virtual Host

    I have not got far with the book so far.  I am still on the second chapter where you set the Virtual Host but after setting up the Dreamweaver site definition and doing the test.  I get the error that page cannot be found.
    I ask if I can mail the text file of the http.conf and the httpd-vhosts.conf to anyone to see if I screwed up somewhere .  I am running on Windows 7 with the WAMP setup.

    Mr. Powers,
    I used your included file httpd-vhosts.conf.  And it did something since now I get a new set of errors.
    ( ! ) Warning: Unknown: failed to open stream: Permission denied in Unknown on line 0
    ( ! ) Fatal error: Unknown: Failed opening required  'C:/vhosts/phpcs5/lesson02/site_check.php'  (include_path='.;C:\php\pear') in Unknown on line 0
    But I checked the properties of the folders and unchecked the 'read only' permission but still gets checked again.  I am using Windows 7 64-bit.
    I checked on the web nobody says any solutions about it, they only imply that is a permissions issue.
    I apologize, I found out the chapter files were encrypted... thanks

  • Installing phpMyAdmin using a virtual host

    The situation:
    Apache services are running (Windows XP SP2).
    Virtual host has been successfully created and works both
    with Dreamweaver php pages and pages entered directly in the
    browser address bar (e.g.
    http://mysite/folder/foo.php.
    Server root is d:\htdocs.
    Sites stored in this server root: d:\htdocs\mysite.
    phpMyAdmin folder stored in the server root
    d:\htdocs\phpMyAdmin.
    My problem:
    I have successfully installed MySql and try to configure
    phpMyAdmin according to the reccomendations in David Powers
    book "PHP solutions". When I start to load the setup php
    using the address:
    http://phpmyadmin/scripts/setup.php
    I am
    automatically connected to the internet and this page is
    loaded
    http://www.phpmyadmin.net/home_page/index.php
    I have then manually modified the config.inc.php and stored
    in the phpMyAdmin root. If I try to launch phpMyAdmin by
    entering
    http://phpmyadmin/ the same page is
    loaded from the
    internet but not phpMyAdmin.
    What have I missed and how can I get phpMyAdmin to work
    properly?
    Paul

    David Powers schrieb:
    > Have you added phpmyadmin 127.0.0.1 to your hosts file?
    Oh no, I should known better ;-) Didn't think of that.
    > Have you set up the virtual host definition for
    phpmyadmin in httpd.conf?
    No, but have done it now. Now I can load phpMyAdmin into my
    browser but I am getting the error "Cannot load mysqli
    although this extension is in my php5/ext folder and it is
    added to config.inc.php
    $cfg['Servers'][$i]['extension'] = 'mysqli'; // The
    php MySQL extension to use ('mysql' or 'mysqli')
    > Quite honestly, though, I don't see any value in
    creating a virtual host
    > for phpmyadmin in your testing environment. The value of
    virtual hosts
    > is mainly to enable the use of site-root-relative links.
    You don't need
    > that for phpmyadmin.
    Ok. So having installed the virtual host for phpMyAdmin just
    lets me test if its running on my PC? Withougt a virtual
    host how can I see if phpMyAdmin works?
    Thanks for your help.
    Paul

Maybe you are looking for