HTTP and WebService interface testing

Interface Request Message Stitching

Url?param=value&param1=value url+?+ parameter = value

The entry parameter is a JSON string and cannot be spliced with a tool, such as: Postman

Get post

If a GET request is entered directly in the browser, you can request a

If it is a POST request, you need to use the tool to send

Get and post differences

1.get use a URL or a cookie to pass parameters, and post in the body (in fact, the POST request can also be placed in the URL)

2.get URL length is limited, and post can be very large; (now the browser has no length limit)

3.post is more secure and cannot be viewed in the address bar, but it is relatively safe to see the data in the capture packet

4. The general get is used to obtain the request data, and the post is used to send the data

Status code for HTTP

200 2 indicates that the request was sent successfully, the most common being 200, indicating that the request was OK, and that the server returned a value

300 3 begins with a redirect, the most common being 302,301, indicating that the request is redirected to another place

400 400 on behalf of the client sent a request syntax error, 401 for the page access is not authorized, 403 means that there is no access to this page, 404 means no This page

500 5 represents a server with an exception, 500 represents an internal server exception, and 504 represents a server timeout

WebService Interface Test

Do not need splicing message, will give a webservice address, or Wdls file, directly in the SOAPUI import, you can see all the interfaces in webservice, there are messages, directly fill in the parameters call, see return results;

http://www.webservicex.net/globalweather.asmx?wsdl

HTTP and WebService interface testing