Access Gateway Access log


Access Gateway access logs include information on HTTP access request events such as GET and POST.

Before you begin

Event Fields

Access Log

Field Description

TIMESTAMP

Current system date and time

HOSTNAME

Hostname of Access Gateway node generating the event

Tag

auth

Application Hostname

Hostname of the application (public domain of application)

Client IP

Clients’s IP address

- -

- -

Request

HTTP request (GET, POST)

URL

Relative URL

HTTP Status Code

HTTP status code (200, 302 etc)

Request size

Size of request body in bytes

HTTP Referrer

Always - (dash)

User Agent

Browser information

X-Forwarded-For

X-Forwarded-For header received

Request Time

Time in seconds to receive request

Response Time

Time in seconds to send a response

 

Event issued on every resource request.

Example access events:

2020-06-24T09:40:43.000-05:00 example.myaccessgateway.com auth header.myexample.com 10.0.0.110 - - "GET / HTTP/2.0" 302 163 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.149 Safari/537.36" "-" 0.073 -

2020-06-24T09:41:08.000-05:00 example.myaccessgateway.com auth header.myexample.com 10.0.0.110 - - "GET /assets/images/image.png HTTP/2.0" 200 1229 "https://gw-admin.example.com/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.149 Safari/537.36" "-" 0.029 0.028

HTTP Status Codes

Access Gateway returns the following status codes to the browser.

HTTP Status Codes

Status Code Description

200

Successful response

302

Redirect

400

Application being accessed using IP address or the hostname not being served by Access Gateway.

401

Session does not exist.

403

Policy rule denied access to resource.

404

Unknown page/content/resource.

405

Session integrity failure.

500

Server side error.

502

Back end application not available.

503

Application is in maintenance, inactive, or offline mode.

504

Request to back end application timed out.