@SprX

You don’t need the ProxyPass configuration unless you’re passing the request over to an address that uses a port other than 80/443. For example, if you were running a NodeJS app that was running on a port such as 2365, and you wanted it to respond on a port 80 (i.e. without having to attach a port to the URL), then you would use ProxyPass.

For a standard domain setup, you really only need

<VirtualHost *:80>
    ServerAdmin webmaster@localhost
    DocumentRoot /path/to/domain01.com
    ServerName domain01.com
    ServerAlias www.domain01.com

    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined

    <Directory /path/to/domain01.com>
        Options Indexes FollowSymLinks MultiViews
        AllowOverride all
        Order allow,deny
        allow from all
        Require all granted
    </Directory>
</VirtualHost>

So if that’s your base and you want domain02.com to point to /new in the same directory as your existing domain, you’d setup another server block and use something such as:

<VirtualHost *:80>
    ServerAdmin webmaster@localhost
    DocumentRoot /path/to/domain01.com/new
    ServerName domain02.com
    ServerAlias www.domain02.com

    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined

    <Directory /path/to/domain01.com/new>
        Options Indexes FollowSymLinks MultiViews
        AllowOverride all
        Order allow,deny
        allow from all
        Require all granted
    </Directory>
</VirtualHost>