Difference between revisions of "Ns respond"
Jump to navigation
Jump to search
(wiki-formatted the page) |
|||
Line 1: | Line 1: | ||
− | ns_respond | + | '''NAME''' |
− | + | : ns_respond - Build a complete response | |
− | + | '''SYNOPSIS''' | |
− | + | : '''ns_respond''' ''?-status status? ?-type type? {?-string string? | ?-file file? | ?-fileid fileid? } ?-length length? ?-headers setId?'' | |
− | + | '''DESCRIPTION''' | |
− | + | : ns_respond builds a complete response for the client with all of the specified information in the header. | |
− | + | '''EXAMPLE''' | |
− | |||
− | ns_respond | + | : Using ns_respond, it's easy to do an HTTP redirect: |
− | |||
− | + | set headers [ns_set new myheaders] | |
− | + | ns_set put $headers location <nowiki>http://www.aolserver.com</nowiki> | |
− | + | ns_respond -status 302 -type text/plain \ | |
− | + | -string "redirection" -headers $headers | |
− | |||
− |
Revision as of 12:22, 6 May 2009
NAME
- ns_respond - Build a complete response
SYNOPSIS
- ns_respond ?-status status? ?-type type? {?-string string? | ?-file file? | ?-fileid fileid? } ?-length length? ?-headers setId?
DESCRIPTION
- ns_respond builds a complete response for the client with all of the specified information in the header.
EXAMPLE
- Using ns_respond, it's easy to do an HTTP redirect:
set headers [ns_set new myheaders] ns_set put $headers location http://www.aolserver.com ns_respond -status 302 -type text/plain \ -string "redirection" -headers $headers