• View Communities
    • Citrix Developer Network
      The place for unfiltered straight talk on Citrix products. Blogs, code downloads, best practices, APIs, and more can all be found here.
    • Citrix Ready Community Verified
      Does it work with Citrix? Application compatibility questions are a thing of the past with the new Citrix Community Verified site.
    • Blogs
      Learn the latest from the Citrix employees who are building application delivery infrastructure technologies.
    • Blogosphere
      The Citrix Blogosphere is a window into the thousands of conversations taking place about Citrix and Application Delivery.
  •  Sign In
NetScaler Developer Network

Internal Variables that can be used for HTML Injection

The list of internal variables supported by the system and can be used for HTML Injection.

Summary

The HTML Injection feature provides a pre-defined set of internal variables that are dynamically replaced with actual system values during run time. This is useful for measuring performance, since you can use these variables to track system values at different points in time.
The table below lists all of the internal variables that can be referenced during HTML injection.

Name Type JavaScript Type Comment
SYS.IID 128 bit GUID structure Windows format GUID This is a GUID that uniquely identifies each Netscaler system. The value of this variable remains constant across reboots. It is valid in both prebody and postbody.
HTTP.XID 128 bit GUID structure Windows format GUID This is a GUID that uniquely identifies each HTTP transaction (request/response). This variable is guaranteed to be unique even if the Netscaler is rebooted. It is valid in both the prebody and postbody.
SYS.UPTIME 32 bit integer 10 digit number Gives the time in seconds, offset to UTC, that the Netscaler system has been up. It is valid in both prebody and postbody.
HTTP.REQ.RECEIVE_TIME_BEG 64 bit integer 20 digit number Gives the time, in microseconds, when Netscaler received the first byte of a client request. It is valid in both prebody and postbody.
HTTP.REQ.RECEIVE_TIME_END 64 bit integer 20 digit number Gives the time, in microseconds, when Netscaler received the last byte of a client request. It is valid in both the prebody and postbody.
HTTP.REQ.SEND_TIME_BEG 64 bit integer 20 digit number Gives the time, in microseconds, when Netscaler forwarded the first byte of a request to the backend server. It is valid in both prebody and postbody.
HTTP.REQ.SEND_TIME_END 64 bit integer 20 digit number Gives the time, in microseconds, when Netscaler forwarded the last byte of a request to the backend server. It is valid in both prebody and postbody.
HTTP.RES.RECEIVE_TIME_BEG 64 bit integer 20 digit number Gives the time, in microseconds, when Netscaler received the first byte of a response from the backend server. It is valid in both prebody and postbody.
HTTP.RES.RECEIVE_TIME_END 64 bit integer 20 digit number Gives the time, in microseconds, when Netscaler received the last byte of a response from the backend server. It is valid only in postbody.
HTTP.RES.SEND_TIME_BEG 64 bit integer 20 digit number Gives the time, in microseconds, when Netscaler forwarded the first byte of response to the client. It is valid in both prebody and postbody.
HTTP.RES.SEND_TIME_END 64 bit integer 20 digit number Gives the time, in microseconds, when Netscaler forwarded the last byte of a response to the client. It is valid only in postbody.

More Information

Tags

appexpert appexpert Delete
code code Delete
prebody prebody Delete
postbody postbody Delete
pe pe Delete
how to how to Delete
html injection html injection Delete
policy filter policy filter Delete
filter policy filter policy Delete
policy engine policy engine Delete
Enter tags to add to this page:
Please wait 
Looking for a tag? Just start typing.
Related Links