JetBrains Rider 2021.3 Help

HTTP Client

With the HTTP Client plugin, you can create, edit, and execute HTTP requests directly in the JetBrains Rider code editor.

Example HTTP request

There are two main use cases when you need to compose and run HTTP requests:

  • When you are developing a RESTful web service and want to make sure it works as expected, is accessible in compliance with the specification, and responds correctly.

  • When you are developing an application that addresses a RESTful web service. In this case, it is helpful to investigate the access to the service and the required input data before you start the development. During the development, you may also call this web service from outside your application. This may help locate errors when your application results in unexpected output while no logical errors are detected in your code and you suspect that the bottleneck is the interaction with the web service.

HTTP requests are stored in .http and .rest files and are marked with the HTTP file icon icon.

Support for HTTP files includes the following features:

If necessary, before you begin, configure the Proxy settings on the HTTP Proxy page of the Settings/Preferences dialog (Ctrl+Alt+S).

Create HTTP request files

You can work with HTTP requests either from scratch files or from physical files of the HTTP Request type. Each file can contain multiple requests, and you can create as many files as needed.

Scratch files can be used to test HTTP requests during development. Scratch files are not stored inside a project, so JetBrains Rider can modify them and add additional information about the request. When an HTTP request is executed from a scratch file, the link to the response output file is added below the request and at the top of the requests history file.

Create an HTTP request scratch file

  • Press Ctrl+Alt+Shift+Insert and select HTTP Request.

  • Switch to the Scratches view in the Solution window, right-click a folder where you want to add the request file and choose Add | HTTP Request from the context menu.

Physical files can be used for documenting, testing, and validating HTTP requests. Physical files are stored inside your project, and JetBrains Rider will not modify them. When an HTTP request is executed from a physical file, this file is not modified. Information about the executed request with the link to the response output file is added to the top of the requests history file.

Create a physical HTTP request file

  • Right-click a folder where you want to add the request file and choose Add | HTTP Request from the context menu.

Move an HTTP request

You can use the Move refactoring F6 to move HTTP requests from scratches to physical files, as well as between physical files.

  1. In the editor, position the caret at the request to be moved and do one of the following:

    • From the main menu or the context menu, select Refactor | Move.

    • Press Alt+Enter and select the Move HTTP Requests context action.

    • Press F6.

  2. In the Move HTTP Requests dialog that opens, do the following:

    • In the Path field, choose one of the existing .http files from the list or click the Browse button to locate the file.

      You can also type the full path to the file manually. If you specify the name of a non-existing file, a new file with the provided name will be created automatically.

    • In the Requests list, select the checkboxes next to the requests you want to move.

Compose HTTP requests

JetBrains Rider uses the HTTP request in Editor format, which provides a simple way to create, execute, and store information about HTTP requests. You can type them directly in the created HTTP request files using the following general syntax:

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

After the ### separator, you can enter any comments preceded by # or //.

To quickly find your request in run/debug configurations, Search Everywhere, and Run Anything, you can give it a name. Enter it above the request, next to ###, # @name, or # @name =.

Enter the HTTP request name

If a request does not have a name, JetBrains Rider will use its position in the .http file, such as #1, as the request name. If a .http file contains multiple requests with the same name, JetBrains Rider will append the request position number to each of the names. This will make each request name unique so that you can easily find the needed one in the Services tool window, run/debug configurations, and so on.

HTTP requests in Services tool window

To speed up composing HTTP requests, click the Add request shortcut link on top of the request's editor panel. In the popup menu, choose the type of the request to add.

Add an HTTP request

Alternatively, use live templates. In the editor, you can press Ctrl+J to view the list of available templates. For example, gtr expands to a simple GET request; mptr expands to a multipart/form-data POST request.

expand_post_template

To get an overview of the HTTP Client possibilities, you can explore the HTTP Requests Collection, which is a handful selection of composed requests.

Open a request from the HTTP Requests Collection

  1. Click the Examples shortcut link on top of the request's editor panel.

  2. In the popup menu, choose the HTTP Requests collection you wish to open:

    Open HTTP Requests Collection popup

Convert cURL requests

If you are working with cURL requests, you can convert between cURL requests and the HTTP request in Editor format.

Convert cURL to HTTP request

  • Paste the cURL request into an HTTP request file. JetBrains Rider will convert it to the HTTP request format and leave the original cURL request commented out for later reference.

    cURL request converted to HTTP request on paste
  • Alternatively, click the Convert shortcut link on top of the HTTP request editor panel and select Convert cURL to HTTP Request, or select Tools | HTTP Client | Convert cURL to HTTP Request from the main menu.

    In the Convert cURL to HTTP Request dialog, type or paste the cURL request that you want to convert.

    the Convert cURL to HTTP Request dialog

Consider the following example cURL request:

curl 'http://httpbin.org/' -H 'Connection: keep-alive' -H 'Accept: text/html' -H 'Accept-Encoding: gzip, deflate' -H 'Accept-Language: en-US,en;q=0.9,es;q=0.8'

JetBrains Rider will convert it to the following:

# curl 'http://httpbin.org/' -H 'Connection: keep-alive' -H 'Accept: text/html' -H 'Accept-Encoding: gzip, deflate' -H 'Accept-Language: en-US,en;q=0.9,es;q=0.8' GET http://httpbin.org/ Connection: keep-alive Accept: text/html Accept-Encoding: gzip, deflate Accept-Language: en-US,en;q=0.9,es;q=0.8 ###

The converter supports the following cURL options:

Option

Description

-X, --request

The request method to use.

-H, --header

The request header to include in the request.

-u, --user

--basic

--digest

The user's credentials to be provided with the request, and the authorization method to use.

-d, --data, --data-ascii

--data-binary

--data-raw

--data-urlencode

The data to be sent in a POST request.

-F, --form

The multipart/form-data message to be sent in a POST request.

--url

The URL to fetch (mostly used when specifying URLs in a config file).

-i, --include

Defines whether the HTTP response headers are included in the output.

-v, --verbose

Enables the verbose operating mode.

-L, --location

Enables resending the request in case the requested page has moved to a different location.

Convert HTTP request to cURL

  1. Put the caret at the HTTP request that you want to convert to cURL format.

  2. Click Alt+Enter and select Convert to cURL and copy to clipboard.

    Alternatively, you can click the Convert shortcut link on top of the HTTP request editor panel and select Convert HTTP Request Under Caret to cURL and Copy.

This will generate a cURL request based on the HTTP request and copy it to the clipboard.

Create requests from OpenAPI specifications

When working with OpenAPI Specification files, you can create HTTP requests to the specified endpoints.

Create an HTTP request to an endpoint

  • In an OpenAPI specification file, click the Open in HTTP Client button in the editor gutter next to the endpoint definition.

JetBrains Rider will create a new HTTP request and save it in the generated-requests.http scratch file.

Rename an endpoint and its usages

Use the Rename refactoring to rename the defined endpoint and its usages in HTTP requests simultaneously.

  1. Do any of the following:

    • In an OpenAPI specification file, position the caret at the endpoint's definition you want to rename.

    • In an HTTP request file, position the caret at the URL path segment you want to rename.

  2. Select Refactor | Rename from the main menu or the context menu, or press Shift+F6.

  3. In the Rename dialog that opens, specify the new endpoint's name.

  4. Preview and apply changes.

JetBrains Rider will rename the endpoint and its usages.

Use response handler scripts

With response handler scripts, you can programmatically react to a received HTTP response. By using these scripts, you can automatically process the received data as well as validate it against the conditions that you specify. Response handler scripts are provided as a part of the request within the HTTP request file and are executed as soon as a response is received. To view the response handling examples, open the Requests with Authorization or Requests with Tests requests collections.

You can insert a response handler script into your request either in-place or by referring to an external file.

Insert the script into the request

  • To insert the script in-place, prepend it with > and enclose it in {% %}:

    GET host/api/test > {% // Response Handler Script ... %}
  • To insert the script from an external file, prepend it with >:

    GET host/api/test > scripts/my-script.js

Response handler scripts are written in JavaScript ECMAScript 5.1, with coding assistance and documentation handled by the bundled HTTP Response Handler library. For in-place scripts, this functionality is enabled automatically. For external scripts, you need to enable it manually.

Enable JavaScript coding assistance for response handler scripts

  1. Open the script file in the editor.

  2. In the context menu, choose Use JavaScript Library | HTTP Response Handler.

The HTTP Response Handler library exposes two objects to be used for composing response handler scripts:

  • The client object stores the session metadata, which can be modified inside the script. The client state is preserved until you close JetBrains Rider. Every variable saved in client.global as variable_name is accessible to subsequent HTTP requests as {{variable_name}}.

  • response holds information about the received response: its content type, status, response body, and so on.

To open the HTTP Response Handler library in the editor, position the caret at the library object and press Ctrl+B.

Response handler scripts can include tests, which lets you use the HTTP Client as a testing framework. To create a test, invoke the client.test(testName, function) method. Inside the test, you can assert a condition by invoking the client.assert(condition, message) method, for example:

GET https://httpbin.org/status/200 > {% client.test("Request executed successfully", function() { client.assert(response.status === 200, "Response status is not 200"); }); %}

Execute HTTP requests

  1. If you are going to test your own web service, make sure it is deployed and running.

  2. Do any of the following:

    • In the editor, click The Run button in the gutter next to the request you want to execute. From the list, select Run <request name>.

    • In the editor, select Run <request name> from the request's context menu.

    • Position the caret at the request you want to execute, press Alt+Enter and select the Run <request name> intention action.

    • If you have multiple HTTP requests defined in an .http file, you can run all of them sequentially. To do this, use the corresponding Run All Requests in File shortcut link on top of the request's editor panel.

    If you have environments defined, select Run with ... and choose the environment in the popup menu. The selected environment will be used as the default one when executing or debugging the request later.

When a request is executed, JetBrains Rider automatically creates a dedicated temporary HTTP Request run/debug configuration for it. You can save it as a permanent run/debug configuration if necessary.

Open a request in the browser

You can open an HTTP request in the browser specified on the Web Browsers and Preview page of the Settings/Preferences dialog (Ctrl+Alt+S).

  • Press Alt+Enter and select the Open in web browser context action.

Open HTTP request in the browser

Work with HTTP request run/debug configurations

When you execute an HTTP request from the editor, JetBrains Rider automatically creates a temporary run/debug configuration with the request parameters. A temporary run/debug configuration works the same way as a permanent run/debug configuration. You can change its settings using the Run/Debug Configuration dialog and optionally save it as permanent.

Modify an HTTP Request run/debug configuration

  1. Do any of the following:

    • In the editor, right-click a request and in the context menu, select Modify Run Configuration.

    • Alternatively, choose Run | Edit Configurations from the main menu, and select the needed run/debug configuration in the HTTP Request list.

  2. Change the needed configuration parameters:

    • In the Environment list, select an environment that will define the set of environment variables used in the request.

    • In the File field, provide the path to the HTTP request file. You can type the path manually and use path completion Ctrl+Space as you type, or click Open from disk and select the required folder in the dialog that opens.

    • If your request file contains multiple requests, in the Request list, choose the name of the request to execute.

Save a temporary HTTP Request run/debug configuration

  • In the Run/Debug Configuration selector, choose Save <configuration name>.

  • In the Run/Debug Configuration dialog, select the configuration and click the Save button.

Execute a request using a run/debug configuration

  • In the Run/Debug Configuration selector, select the desired run configuration. Then click Run button on the main toolbar or press Shift+F10.

  • Press Alt+Shift+F10, select the desired run configuration from the list, and press Enter.

View responses from web services

When you execute an HTTP request, JetBrains Rider automatically saves the response into a separate file under the .idea/httpRequests/ directory. You can view the 50 most recently stored responses and navigate to the corresponding files using the requests history. If the request was executed from a scratch file, the link to its response output is also added below the original request:

HTTP response

View a received response

  1. Switch to the Services tool window, which opens automatically as soon as a response is received.

  2. By default, the server response is shown in the format specified in the request header via the content-type field. To have the response converted into another format, click Response view settings and select Text, JSON, XML, or HTML.

    HTTP response in the Services tool window

If you have a response handler script, the results of the tests executed as part of this script are displayed on the Tests tab of the Services tool window.

The Tests tab of the Services tool window

If the response is an image, you'll see its preview in the Services tool window.

HTTP response with an image

If you subscribe to Server-Sent Events, JetBrains Rider displays them in the Services tool window. Here, you can also view the status of the client-server connection and terminate it by clicking Stop. Depending on the content type (either text/event-stream or application/x-ndjson), the response will be formatted as plain text or newline-delimited JSON.

Server-sent events

Redirecting Server-Sent Events to a file is currently not supported.

Open a response file in the editor

  • Position the caret at the link to the response you want to open, and choose View | Jump to Source from the main menu, or press Ctrl+B or F4.

  • Ctrl+Click the response line:

    Open the response tooltip

Compare responses in a scratch file

When a request is executed from a scratch file, the link to the response output file is added below the original request.

  • Do any of the following:

    • Position the caret at the link to the response file. Press Alt+Enter and select the Compare with <response name> intention action.

    • Click Compare responses in the gutter and select Compare with <response name> from the list:

      Compare responses in request history

Compare responses in the requests history

When a request is executed from a physical file, the link to the response output is added to the requests history.

  1. Position the caret at the link to the response file. Choose View | Jump to Source from the main menu, or press Ctrl+B or F4 to open this file in a new editor tab.

  2. Choose View | Compare With from the main menu, or press Ctrl+D. JetBrains Rider will prompt you to open a response file from the httpRequests folder.

  3. Select the response file you would like to compare the current file with and click Open.

The two response files will be opened in the Differences viewer allowing you to compare their contents:

Compare HTTP responses

View request history

JetBrains Rider automatically saves the 50 recently executed requests into the http-requests-log.http file, which is stored on the project level under the .idea/httpRequests/ directory. With requests history, you can quickly navigate to a particular response as well as issue any request again. If a request is issued again from the request history, its execution information and the link to the response output are added to the top of the request history file.

Open requests history

  • Click the Open Log shortcut link on top of the request's editor panel.

  • Select Tools | HTTP Client | Show HTTP Requests History from the main menu.

Requests history

Redirect output to a custom file or directory

  • The HTTP Client can redirect output to a custom file or directory. It supports two operators for force and soft redirects:

    • The >> operator always creates a new file, adding an -n suffix to a filename if the requested filename already exists.

    • The >>! operator rewrites the file if it already exists.

Manage cookies

The cookies received through a response are automatically saved into the dedicated http-client.cookies file under the .idea/httpRequests/ directory. The number of cookies that can be saved is limited to 300. The name and value of a cookie are automatically included in each subsequent request to the URL that matches the domain and path specified for the cookie, provided that the expiry date has not been reached.

the http-cookies file

If you want to set custom cookies in an HTTP request, you can use the Cookie header. Enter your cookies as a list of name=value pairs separated by a semicolon, for example:

GET http://localhost:80/api Cookie: theme=dark; country=France

gRPC requests

The HTTP Client supports gRPC requests. For the HTTP Client to treat your requests as gRPC requests, start them with the GRPC keyword.

The HTTP Client provides completion for gRPC: all known gRPC services, unary and server-streaming methods of a particular server, and fields of accepted messages in the request body.

HTTP Client supports gRPC requests

Generate a gRPC request from PROTO files

  • In the PROTO file, click the Generate icon near the RPC method.

    Generate a gRPC request from PROTO files

Configuring proxy settings

  1. In the Settings/Preferences dialog (Ctrl+Alt+S), choose System Settings under Appearance & Behavior, then choose HTTP Proxy.

  2. In the Proxy dialog that opens, select Manual proxy configuration and specify the following:

    • Enter the proxy host name and port number in the Host name and Port number fields.

    • To enable authorization, select the Proxy authentication checkbox and type the username and password in the corresponding fields.

Last modified: 07 April 2022