ZuploRequest inherits from the web standard
Request class used with
you can read more about this on MDN including an explanation of how all of its
properties and methods work:
In addition to the standard properties, the following are added for convenience.
params- if you use tokens in your route’s URL, we automatically parse them into properties on the params property of your request. For example, imagine a route with path
/products/:productId/vendors/:vendorId. A match on this would yield values as follows:
user- an optional object identifying a ‘user’. If
undefinedthis typically means the request is anonymous. If present, the user object will have a
subproperty that is a unique identifier for that user. There is also an optional
dataproperty that is of
anytype that typically contains other information about the user. When using JWT tokens you’ll usually find all the claims here.
query- a dictionary of query-string values. For example, a URL with a query string like
https://example.com?foo=barwould present as follows:
It can be useful to create a new ZuploRequest inside a policy (see policies) to forward to the next policy or handler in the chain. You can create a completely fresh ZuploRequest as follows: