%CSP.Request

• request.CgiEnvs(<NAME>)=<VALUE>

• request.Cookies(<NAME>,<INDEX>)=<VALUE>

• %request.Data(<NAME>,<INDEX>)=<VALUE>
• %request.Data(<NAME>,<INDEX>,"encrypt")=<Encrypted state>
• %request.Data(<NAME>,<INDEX>,"O")=<Order number item was added>

  ; Set the index number one 'Name' to 'Value'
  Set %request.Data("Name",1)="Value"
  ; Output the value of parameter 'Name' for index number one (the default)
  Write %request.Data("Name",1)
  ; Insert a new value for parameter 'Name' to 'Value'
  Set %request.Data("Name",$Order(%request.Data("Name",""),-1)+1)="Value"
  ; Test if parameter 'Name' at index 2 is encrypted
  If $Data(%request.Data("Name",2,"encrypt"))
  

If InterSystems IRIS receives a value that is longer than the string length limit, it automatically creates a stream, writes the value to that stream, and places the stream OREF into the Data property in place of the actual value. This means that in any case where you might receive a very long string, your code should examine the value to see if it is an OREF, and then handle it accordingly:

   Set value=%request.Data("fieldname",1)
   If $isobject(value) { 
     ; Treat this as a stream 
   } Else { 
     ; Treat this as a regular string
   }
  

• request.MimeData(<NAME>,<INDEX>)=<VALUE>

If more than one value is associated with name, then the values are subscripted using index starting with 1. Note that any encrypted parameters will have lower index values than any unencrypted parameters, and so will come first when you loop through them.

If the name-value pair is not defined, returns the value of default.

It is recommended to access the Data property directly because it is faster. For example, this call is equivalent to:

  Set return=$Get(%request.Data(name,index),default)
  

If more than one value is associated with name, then the values are subscripted using index starting with 1.

It is recommended to access the Data property directly because it is faster. For example, this call is equivalent to:

  Set %request.Data(name,$Order(%request.Data(name,""),-1)+1)=value
  

It is recommended to access the Data property directly because it is faster. For example, this call is equivalent to:

  Set return=$Data(%request.Data(name,index))
  

It is recommended to access the Data property directly because it is faster. For example, this call is equivalent to:

  Set return=$Get(%request.Data(name,index,"encrypt"),0)
  

It is recommended to access the Data property directly because it is faster. For example, this call is equivalent to:

  Set return=$Order(%request.Data(name))
  

It is recommended to access the Data property directly because it is faster. For example, this call is equivalent to:

  Set index=$Order(%request.Data(name,index),1,return)