The Apache access log (access.log) contains a list of requests for your application (glossary term, activate to view definition) that have bypassed Varnish®. These requests include pages, theme files, and static media files.
Each of the items in the Apache access log is noted in the following table, along with its description:
Position
Data
Description
0
200.0.0.1
The remote host (client IP).
1
-
The identity of the user determined by identd. Rarely used.
2
-
The user name, determined by HTTP authentication.
3
[04/Jan/2017:23:20:38+0000]
The date and time the request was received by the backend infrastructure.
4
"GET/contact_usHTTP/1.1"
Apache access logs
The Apache access log (access.log) contains a list of requests for your application (glossary term, activate to view definition) that have bypassed Varnish®. These requests include pages, theme files, and static media files.
The user-agent, or browser identification string, encased in quotation marks as many browser names have spaces in them.
9
vhost=alphabeta.prod.acquia-sites.com
The underlying virtual host matching the requested domain name.
10
host=www.example.com
The domain name for the request, which does not have to match the virtual host (vhost) name.
11
hosting_site=alphabeta
The internal Acquia site name this request is for.
12
pid=26731
The process ID (pid) on the infrastructure that handled this request.
13
request_time=10186417
The time needed to serve the request, in microseconds (1/1000000 of a second).
14
forwarded_for="200.0.0.1,162.0.0.1"
The full set of IP addresses tracked as “requester IP,” which will contain the IP addresses of the following if they are in use by the subscription (glossary term, activate to view definition):
Load balancer
ELB (Elastic Load Balancer (glossary term, activate to view definition))
Content Delivery Networks or Web Application Firewalls (WAFs) such as Edge)
A unique ID attached to this request by the load balancer, which appears in several Cloud Platform log files. For more information, see Using HTTP request IDs.
16
location="http://apache.example.com/"
The contents of the Location HTTP header.
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
The REQUEST line from the client, containing three parts:
The method of the request (GET)
The path requested (/contact_us)
The HTTP protocol (1.1)
5
404
The HTTP status code sent from the infrastructure to the client. Production environments don’t display full information for HTTP 5xx status codes.
6
10117
The total size, in bytes, of the response to the client.
7
"-"
The referrer, which is the page (none in this case) that provided the link to this page.
The user-agent, or browser identification string, encased in quotation marks as many browser names have spaces in them.
9
vhost=alphabeta.prod.acquia-sites.com
The underlying virtual host matching the requested domain name.
10
host=www.example.com
The domain name for the request, which does not have to match the virtual host (vhost) name.
11
hosting_site=alphabeta
The internal Acquia site name this request is for.
12
pid=26731
The process ID (pid) on the infrastructure that handled this request.
13
request_time=10186417
The time needed to serve the request, in microseconds (1/1000000 of a second).
14
forwarded_for="200.0.0.1,162.0.0.1"
The full set of IP addresses tracked as “requester IP,” which will contain the IP addresses of the following if they are in use by the subscription (glossary term, activate to view definition):
Load balancer
ELB (Elastic Load Balancer (glossary term, activate to view definition))
Content Delivery Networks or Web Application Firewalls (WAFs) such as Edge)
A unique ID attached to this request by the load balancer, which appears in several Cloud Platform log files. For more information, see Using HTTP request IDs.
16
location="http://apache.example.com/"
The contents of the Location HTTP header.
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Cloud Platform