Apache configuration: .htaccess

Deploy Now uses Apache HTTPD server in a shared infrastructure environment. As a result users do not have rights to edit the main server configuration file on there own. However you can define your own configuration via .htaccess.


A .htaccess file is a common way to make configuration changes on per-directory basis. A .htaccess file can have multiple configuration directives at once. All configuration directives applies to the directory in which the .htaccess file resides and all subdirectories. It's good to know that each directory can define it's one .htaccess file. Directives are applied in the order that they are found. A directive found high up in the directory tree can override all directives found before or even defined by the Apache main configuration itself.

Redirects and Rewrites

A redirect or forward directive instructs the client to switch URLs and navigate to the destination of the directive. The class of 3xx - HTTP status codes indicates such redirects. This means that the client must take an additional action to complete the request. Your browser perform this action automatically and you can notice this by a change to the new URL of the directive in your browser bar. Redirects are often used to redirect an old path to a new one or make content available under more than one URL.

In contrast, a rewrite directive instructs the server to serve the content of the directive destination at the original URL. The browser won't notice anything of this directive. This kind of technique grew in popularity for client-side routing in Single Page Applications (SPAs) where all requests are handled via index.html.

You find various sample snippets for redirects or rewrites here and you can use our .htaccess sample as playground.


Choosing the right configuration can be a great booster for web security and the good news is, it's much easier as you probably think. The following paragraph should give you some ideas and further links.

HTTP Security Headers

HTTP Security Headers are a subset of HTTP headers and are exchanged between a web client and a server to specify the security-related details of HTTP communication. Some HTTP headers that are indirectly related to privacy and security can also be considered HTTP security headers. By enabling suitable headers in web applications and web server settings, you can prevent security vulnerabilities like Cross-Site Scripting, Clickjacking, Information disclosure and much more.

The OWASP foundation is an online community that provides a lot of freely-available security information about web application security.The OWASP HTTP Security Response Headers Cheat Sheet gives you a brief overview of all security-related HTTP headers.

In our .htaccess sample you can easily notice the difference in getting a security summary A+ or F rank.

Best practices

Not all best practices are necessary at any time. The simple answer is: „It depends …“. Some of them are almost universal and some depend on your individual use case. Here comes the list of the almost universal rules:

  1. Force HTTPS - Good news: "Deploy Now does this by default and allows HTTPS only."
  2. Deny access to hidden files and directories: RedirectMatch 404 /\..*$
  3. Disable directory browsing: Options All -Indexes

You can find other samples here and you can use our .htaccess sample as playground.

Password protection

Password protection via basic authentication is technical possible. But the reference path to your AuthUserFile needs to be absolute. This information isn't public available in Deploy Now at the moment. We will provide a solution soon.

Templating .htaccess

Some frameworks expect additional directives by default. For this case Deploy Now offers the opportunity to add a .htaccess.template in your .deploy-now/ folder. The file itself works just like a normal .htaccess file and is simple copied to the root context of your web project. This ensures that all directives apply to all levels.

Frameworks that requires directives

A list of directives for some commonly used frameworks.


In Laravel the entry point for all incoming requests is ìndex.php located in the /public directory. You need to adapt this entry point by redirecting all requests to this folder structure:

# check that mod_rewrite is enabled
<IfModule mod_rewrite.c>

# enable the runtime rewrite engine
RewriteEngine On

# serve existing files from /public folder as if they were in your base directory
RewriteCond %{REQUEST_URI} !public/
RewriteRule (.*) /public/$1 [L]

# route everything else to /public/index.php
RewriteRule ^ /public/index.php [L]


Single Page Apps like Angular, ReactJS, Vue.js

With Single Page Apps (SPAs) client-side routing has become very popular. Client side routing is a type of routing where as the user navigates around the SPA no full page reload takes place. That's even the case when the page URL changes. Instead, JavaScript is used to update the URL and fetch and display new content. For that reason you need to ensure that your URLs will reach your router. Usually this is done by redirecting all requests to the entry point of your SPA:

# check that mod_negotiation is enabled
<IfModule mod_negotiation.c>
  # diable MultiViews to prevent the Apache behavior of indexing a directory
  Options -MultiViews

# check that mod_rewrite is enabled
<IfModule mod_rewrite.c>

  # enable the runtime rewrite engine
  RewriteEngine On
  RewriteBase /

  # stop processing any other rule set if index.html is requested
  RewriteRule ^index\.html$ - [L]

  # route everything else to /index.html
  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteCond %{REQUEST_FILENAME} !-d
  RewriteRule . /index.html [L]


Nuxt v3 is using Native ES Modules. The mime type *.mjs is not that popular so far. At the moment you have to add the type on your own.

# check that mod_mime is enabled
<IfModule mod_mime.c>
  # add support for ECMAScript modules
  AddType text/javascript js mjs