Represents the outgoing HTTP response in ZPE web execution. The web runtime creates it and exposes it through the RESPONSE value; it is not normally constructed with new ResponseObject().
Response functions configure status codes, headers, text or binary bodies, downloads, redirects, JSON output, and session values. All functions require permission level 0.
Availability: The Response object is documented as part of ZPE 1.14.4. Text, binary, and downloadable response bodies were added in ZPE 1.14.11.
Object functions
- binary [1.14.11+]
Sets a binary ByteStream as the response body.
- body [1.14.11+]
Sets the text response body.
- download [1.14.11+]
Sends a ByteStream as a downloadable file.
- get_header [1.14.4+]
Returns a response header, or all response headers when no name is supplied.
- json [1.14.4+]
Encodes a value as the JSON response body.
- redirect [1.14.4+]
Redirects the client to another URL.
- set_header [1.14.4+]
Sets an HTTP response header.
- set_http_response [1.14.4+]
Sets the HTTP response status code.
- set_session_variable [1.14.4+]
Sets a response session value.
Example
RESPONSE->set_header("Content-Type", "application/json") RESPONSE->set_http_response("200") RESPONSE->body("{\"ok\":true}")
There are no comments on this page.
Comments are welcome and encouraged, including disagreement and critique. However, this is not a space for abuse. Disagreement is welcome; personal attacks, harassment, or hate will be removed instantly. This site reflects personal opinions, not universal truths. If you can’t distinguish between the two, this probably isn’t the place for you. The system temporarily stores IP addresses and browser user agents for the purposes of spam prevention, moderation, and safeguarding. This data is automatically removed after fourteen days. Your email address is stored so that replies can be sent to your email address.
Comments powered by BalfComment