What you'd like to see, if you're concerned about bandwidth usage, is a lot of 304 responses - meaning that the file didn't have to be delivered because they already had a cached version. A 404 code may indicate that you have a problem - a broken internal link or someone linking to a page that no longer exists. (FMLS) 3 beds, 2 baths, 1239 sq. House located at 304 Apache Dr, Canton, GA 30115 sold for $142,000 on Apr 29, 2016. Patio Home-Fenced rear yard-Needs TLC.
- Resolution: Incomplete
- Fix Version/s: None
Apache 304 Error
I am getting an out of memory while running my Junits from mvn test. The MAVEN_OPTS has been specified to 512m which is more than what is needed to run my tests.
When I print available memory to my tests it shows 1M to 63M only.
Is there any other place where it picks the memory args from.
I could see there are some junit properties that can be set but I am not sure where and how should I be setting those properties. I tried setting them in POM.xml but they are not being pickedup.
The same tests are successfully running from within eclipse with same memory args as specified in MAVEN_OPTS.
- Punit Mishra
- 1Vote for this issue
- 1Start watching this issue
Learn how to set up custom error pages in Apache. The Apache web server provides a default set of generic error pages for 404, 500, and other common Apache errors.
However, creating custom error pages allows you to:
- Continue your branding on these pages
- Integrate their design into the look and feel of your website
- Direct lost visitors to their intended destinations
- Provide error pages in languages other than English
- Cloud Server running Linux (CentOS 7 or Ubuntu 14.04)
- Apache installed and running
vServer (VPS) from IONOS
Low-cost, powerful VPS hosting for running your custom applications, with a personal assistant and 24/7 support.
Create the Custom Error Page
First, you will need to create the custom error page. For testing purposes, we will create an example error page to handle 404 errors.
Use SSH to connect to your server and go to your website's document root. Create a new page named my-404.html with the command:
Save and exit the file.
You can view the file by going to http://example.com/my-404.html to make sure it is displaying correctly.
Configure Apache to Use the Custom Error Page
To tell Apache to use a custom error page, you will need to add an ErrorDocument directive. The syntax for this directive is:
For this example, since the my-404.html file is in the site's document root, we will be adding the directive:
This directive needs to go inside the VirtualHost command block in the site's main Apache configuration file.
By common convention, this Apache configuration file is usually:
- CentOS 7/etc/httpd/conf.d/example.com.conf
- Ubuntu 14.04/etc/apache2/sites-available/example.com.conf
The location and filename of a site's Apache configuration file can vary based on how you or your server administrator has set up hosting.
Edit this file with your editor of choice, for example with the command:
- CentOS 7sudo nano /etc/httpd/conf.d/example.com.conf
- Ubuntu 14.04sudo nano /etc/apache2/sites-available/example.com.conf
Scroll through the file until you find the VirtualHost command block, which will look like:
Add the ErrorDocument to the VirtualHost command block, but be sure to put it outside any Directory command blocks. For example:
Save and exit the file, then restart Apache for the changes to take effect:
- CentOS 7sudo systemctl restart httpd
- Ubuntu 14.04sudo services apache2 restart
3040 Apache St
Finally, test your error document by going to an invalid URL for your website. You will be redirected to your new custom 404 page instead.
Apache 304 Error
Other HTTP Error Codes
The most common custom error page is for a 404 error. However, you may want to create custom error pages for other Apache errors as well.
Apache Error 304
These pages can be configured for any 4xx or 5xx error code. A full list of these HTTP error codes can be found on Wikipedia.