...
| Code Block |
|---|
| title | Example of a Request File with Header |
|---|
|
POST /parabank/services/bank/billpay?accountId=54321&amount=100 HTTP/1.1
Host: parabank.parasoft.com
Connection: keep-alive
Content-Length: 160
Accept: application/json, text/plain, */*
Content-Type: application/json;charset=UTF-8
Origin: https://parabank.parasoft.com
Referer: https://parabank.parasoft.com/parabank/billpay.htm
Accept-Encoding: gzip, deflate
Accept-Language: en-US,en;q=0.9
Cookie: JSESSIONID=C86B598044C4F61C21A0DCFE019AC19B
{
"address": {
"street": "West 57th Street",
"city": "New New YorkManhattan",
"state": "NY",
"zipCode": "10019"
},
"name": "Hubert J. Farnsworth",
"phoneNumber": "212-123-4567",
"accountNumber": "56789"
} |
...
For example, consider the following XML payload in a request file without headers:
| Code Block |
|---|
| title | Example of a Request File without Header |
|---|
|
{
"address": {
"street": "West 57th Street",
"city": "New New York",
"state": "NY",
"zipCode": "10019"
},
"name": "Hubert J. Farnsworth",
"phoneNumber": "212-123-4567",
"accountNumber": "56789"
} |
<customerDetails>
<address>
<street>West 57th Street</street>
<city>Manhattan</city>
<state code="NY">New York</state>
<zipCode>10019</zipCode>
</address>
<name title="Prof.">Hubert J. Farnsworth</name>
<contactDetails>
<phoneNumber type="home">212-123-4567</phoneNumber>
</contactDetails>
<accountDetails>
<accountNumber>56789</accountNumber>
</accountDetails>
</customerDetails> |
You can exclude certain traffic patterns from the request matching process using the Exclude Patterns for Request Message Correlation table. For example, if you want to ignore the "phoneNumber" element and the "type" attribute" when matching requests, you could enter the following:
| Element Name | Value Pattern (Use Regular Expressions |
|---|
)Copying Request and Response Messages from HTTP Traffic Files
...