Skip to main content

Citrix Netscaler Custom Log Format

This is an example log format for citrix netscaler:

logFormat Custom %h %l %u [%t] "%r" %s %B "%{Referer}i" "%{User-agent}i"

%h : The remote host.

%l : The remote log name (from identd, if supplied).

%u : The remote user (from auth; may be bogus if return status (%s) is 401).

%t : The time, in common log format (standard English time format).

%r : The first line of the request.

%s : For requests that were redirected internally, this is the status of the original request.

%B : The bytes sent, excluding the HTTP headers (response size).

%{Referer}i : The contents of theReferer: header line(s) in the request sent to the server. The system supports the User-Agent, Referer and cookie headers.

%{User-agent}i : The contents of the User-agent: header line(s) in the request sent to the server. The system supports the User-Agent, Referer and cookie headers.

Example log record: - - [29/Nov/2012:02:30:00 +0200] "GET /test.action?type=a&id HTTP/1.1" 200 4527 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +"


Popular posts from this blog

Creating Multiple VLANs over Bonding Interfaces with Proper Routing on a Centos Linux Host

In this post, I am going to explain configuring multiple VLANs on a bond interface. First and foremost, I would like to describe the environment and give details of the infrastructure. The server has 4 Ethernet links to a layer 3 switch with names: enp3s0f0, enp3s0f1, enp4s0f0, enp4s0f1 There are two bond interfaces both configured as active-backup bond0, bond1 enp4s0f0 and enp4s0f1 interfaces are bonded as bond0. Bond0 is for making ssh connections and management only so corresponding switch ports are not configured in trunk mode. enp3s0f0 and enp3s0f1 interfaces are bonded as bond1. Bond1 is for data and corresponding switch ports are configured in trunk mode. Bond0 is the default gateway for the server and has IP address Bond1 has three subinterfaces with VLAN 4, 36, 41. IP addresses are,, respectively. Proper communication with other servers on the network we should use routing tables. There are three

Listing Zimbra Accounts with Some Details

Recently I have to export the user list for a particular domain. Luckily Zimbra has Admin GUI with a search feature. When you search accounts, you can download search results as a comma-separated csv file. So I did a search and download the result file, but the result did not have all the columns I need and also there is no option for customizing columns for search results. So I had to write a bash script to get the desired list. Here is the bash script ( It can be customized by adding or removing field names. Run it under zimbra user like ./ <domain_name_here> ):