DataGrip 2018.3 Help

Exploring the HTTP request in Editor syntax

To compose an HTTP request in the DataGrip code editor, use the following general syntax:

Method Request-URI HTTP-Version Header-field: Header-value Request-Body

The HTTP request in Editor format introduces additional capabilities, as demonstrated by the following examples. For details on working with HTTP requests, see HTTP Client in DataGrip Code Editor.

Use comments in HTTP requests

  • Within a request, start any line with with // or # to make it a comment line.

    // A basic request GET

Use short form for GET requests

  • For GET requests, you can omit the request method and only specify the URI.

    // A basic request

Compose several requests in a single file

  1. Mark the end of a request by typing the ### separator below it.

    // A basic request ###
  2. Compose another request below the separator.

    // A basic request ### // A second request using the GET method

Break long requests into several lines

  • Indent all query string lines but the first one.

    // Using line breaks with indent GET /api /html /get ?id=123 &value=content

Access a web service with authentication

  • Depending on the web service you are accessing, provide the basic or digest Authorization header.

    // Basic authentication GET Authorization: Basic username password ### // Digest authentication GET Authorization: Digest username password

Enable or disable following redirects

Depending on the web service you are accessing, you may want HTTP requests to either follow redirects or not. When a redirect is followed, the redirected page response is returned; otherwise, the actual redirect response header (such as 301 or 302) is returned.

  • Before the request, add a comment line with the @no-redirect tag.

    // @no-redirect

Provide the request message body

  • Inside the request, prepend the request body with a blank line and do one of the following:

    • Type the request body in place:

      // The request body is provided in place POST HTTP/1.1 Content-Type: application/json Cookie: key=first-value { "key" : "value", "list": [1, 2, 3] }

      If you set the Content-Type header field value to one of the languages supported by DataGrip, then the corresponding language fragment will be auto-injected into the HTTP request message body. If Content-Type is not specified, you can inject a language fragment manually. For more information, see Language injections.

    • To read the request body from a file, type the < symbol followed by the path to the file.

      // The request body is read from a file POST Content-Type: application/json < ./input.json

Use multipart/form-data content type

  • Set the request's Content-Type to multipart/form-data. To send a file as part of the multipart/form-data message, include the filename parameter in the Content-Disposition header.

    POST HTTP/1.1 Content-Type: multipart/form-data; boundary=boundary --boundary Content-Disposition: form-data; name="first"; filename="input.txt" // The 'input.txt' file will be uploaded < ./input.txt --boundary Content-Disposition: form-data; name="second"; filename="input-second.txt" // A temporary 'input-second.txt' file with the 'Text' content will be created and uploaded Text --boundary Content-Disposition: form-data; name="third"; // The 'input.txt' file contents will be sent as plain text. < ./input.txt --boundary--
Last modified: 6 February 2019