Application Options

Help Topics
To manage application options, select menu option Tools/Application Options.

General

  • Show welcome window on startup; if this option is turned on, HttpMaster will open welcome window on startup with the most common actions available.
  • Open last used project on startup; if this option is turned on, last open project will automatically be opened when HttpMaster starts. If last open project is not available, HttpMaster will display empty environment. This setting is relevant only if welcome window is disabled; if welcome window is enabled, you can open last used project from the welcome window.
  • Check for updates on startup; if this option is turned on, HttpMaster will check for updates at application startup and will notify you if a new version is available for download. If new version is available, HttpMaster displays special icon and link in the toolbar of the main window. Even if this option is turned off, you can check for updates manually anytime with the corresponding menu option in the main application window.
  • Show special offers for Professional Edition; if this option is turned on, the application will display available special offers for Professional Edition. This information will be displayed in the main window toolbar; special button will be available where you will be able to get more info about the offer.
  • Save error details to log file; if this option is turned on, the application will save data of all unhandled application errors to error log which will be located in the application's working folder. This option is helpful in the case of a bug in the application to provide additional data about the problem. The name of the log file will be HttpMaster.Error.txt.
  • Display warning message when project from the previous version is opened; if this option is turned on, the application will display warning message if the project you are trying to open was last saved with the previous HttpMaster version.
  • Save new projects to disk in minified form; if this option is turned on, all new projects will be saved to disk as minifed XML. If turned off, new projects will be saved as indented XML. This property can be overriden for a particular project when saving it to disk with Save Project As (Advanced) menu option.
  • Remember last selected request item for each project; if this option is turned on, last selected request item will be remembered for each project and will be automatically selected when the project will be opened.
  • Default encoding for new projects; the encoding specified here is used as the project file encoding and as the request character encoding for every new project. This property can also be set in project properties.
  • Default execution timeout for new projects; the value specified here is used as the default execution timeout for every new project. It is also default timeout value for plain basic requests that are executed in the basic request window. For more info on execution timeout, see the corresponding topic.

Tabs

  • Show close button; if this option is turned on, a close button will be shown on the currently selected tab.
  • Close tab with double-click; if this option is turned on, you will be able to close some tabs (open request item tab, open basic request tab, etc.) with double-click.
  • Close tab with middle-click; if this option is turned on, you will be able to close some tabs (open request item tab, open basic request tab, etc.) with middle mouse button click.
  • Reorder tabs with drag and drop; if this option is turned on, you will be able to reorder some tabs (open request item tab, open basic request tab, etc.) with drag and drop.
  • Display confirmation when more than 10 tabs will be opened; if this option is turned on, the application will display confirmation message if you try to open more than 10 tabs simultaneously.

Execution

  • Start executing request items immediately after the execution window is opened; execution of the selected request items is performed in the special execution window where you have the option to start the execution, stop the execution, view results, etc. If this option is turned on, the execution of the request items will start immediately after the execution window is opened. If turned off, you will have to start execution manually inside the execution window.
  • Display confirmation message before starting request item execution in the main window; if this option is turned on, confirmation message will be displayed in the main window for the following actions:
    • Executing request item in the open tab.
    • Executing selected request items.
    • Executing all request items.
    • Executing request items from the execution group.
    • Executing selected request item in basic request window.
    Important
    For all above actions except Executing selected request item in basic request window, this option is only relevant if Start executing request items immediately after the execution window is opened is turned on. If execution is not set to start immediately after the execution window is opened, confirmation message won't be displayed even if this option is turned on.
    For the action Executing selected request item in basic request window confirmation message is always displayed if this option is turned on.
  • Ensure that currently executing item is visible in the execution window; if this option is turned on, HttpMaster will focus currently executing request item in the execution window. This will ensure that executing item is always visible by scrolling it in the current view, if necessary.
  • Play system sound when execution stops; default system sound will be played when the execution batch completes or is unexpectedly stopped. This setting only affects execution in the execution window.
  • Support URLs with international domain names; if this option is turned on, HttpMaster will be able to execute requests against internet resources that have non-ASCII characters in their domain names.
  • Execute multiple request items according to; when executing multiple request items in the main window, you can select the order in which you want to execute them. The following options are available:
    • Current position of request item in the list; this will always execute selected request items in the order in which they are currently displayed in the main window.
    • Execution order value of request item; this will always execute selected request items in the fixed execution order value set for each request item. This option guarantees that selected request items will always execute in the same order no matter how request items are currently sorted in the main window. See the corresponding topic on how to manually set execution order value.
  • Specify folder for storing temporary files needed by the execution engine; execution engine stores internal execution data on a disk. By using disk, the memory pressure during execution is greatly reduced and it is possible to execute a lot of requests during one execution session without consuming a lot of memory. If custom disk folder is not specifed, HttpMaster uses temp folder of the current user. In any case, these stored internal files are deleted automatically by the application when no longer needed. Storing execution data can be completely disabled in project properties. If disabled, requests will execute much faster, but execution data won't be available for review.

Response and request data

  • Show line numbers when displaying data with pretty viewers; if this option is turned on, all viewers for pretty formatting of data will include line numbers to the left of the displayed content.
  • Enable code folding (outlining) when displaying data with pretty viewers; if this option is turned on, all viewers for pretty formatting of data will display markers for expanding/collapsing code sections.
  • Show indent guide lines when displaying data with pretty viewers; if this option is turned on, all viewers for pretty formatting of data will display vertical structure guide lines.
  • Wrap request and response text data to the beginning of the next line; if this option is turned on, some multi-line request and response data fields (request headers, request body, response body, etc.) will wrap text when line width exceeds width of the containing field (horizontal scrollbar won't be available). This ensures that each line fits viewable window, allowing text to be read from top to bottom without horizontal scrolling.
  • Default pretty viewer for response data; HttpMaster supports pretty display of response body data and by default autoselects the most appropriate viewer based on the response body content type. With this setting you can instruct HttpMaster to always display response body with the specific pretty viewer no matter of the response content type.
  • Use selected pretty viewer for unrecognized content types only; this option can be managed only if some specific pretty viewer is selected in the previously described drop down (it is disabled for 'Autoselect' viewer). If this option is unchecked, HttpMaster will always try to display response data with the specified default pretty viewer even if response data could be better displayed with some other pretty viewer. If this option is checked, HttpMaster will first try to find the most appropriate pretty viewer for the display. If such pretty viewer is not found (possibly due to unrecognized response content type), the specified default pretty viewer will be used.
  • Default content type for request data; with this setting you can instruct HttpMaster to always set content type to the specific value when specifying data to upload. If this setting is empty, HttpMaster will automatically set content type based on the value of 'Upload data type'.
  • Request and response body font; specify font type and size for display of request and response body data. This setting applies to fields that display request body (basic request window, request item properties, execution results) and response body (execution results).
  • Font colors in pretty viewers; select desired type from the dropdown list and then click on a colored area to customize font color with a color picker.

Connection proxy

This section enables you to specify proxy for communication with the internet. If proxy is specified, HttpMaster will use it for all internet communication. The following options are available:
  • Proxy address; specify proxy address, for example, IP address.
  • Proxy requires authentication; if this options is turned on, you will have to specify authentication credentials to be used. The following options are available:
    • Default; HttpMaster will use credentials of the current Windows user.
    • Network; you will have to manually specify credentials that HttpMaster should use.
Specified proxy can be enabled/disabled in the main window with the corresponding menu option or with a shortcut Ctrl+Shift+P.

Curl options

In Professional edition, you can prepare curl commands from selected project request items and these options enable you to customize these prepared commands. Curl options can also be accessed directly in the window where curl commands are prepared.

OpenAPI options

This section enables you to customize how OpenAPI data is handled when creating HttpMaster project from it. The following options are available:
  • OpenAPI data used for project request item name; here you can set which OpenAPI data element will be used for HttpMaster request item name. Note that request item names in HttpMaster project must be unique.
  • OpenAPI data used for project request item description; here you can set which OpenAPI data element will be used for HttpMaster request item description. Because request item description is optional, you can select None to leave request item description blank.
  • Prevent creating multiple project request items with the same operation ID; if turned on, error message will be displayed when creating or updating the project if multiple items with the same operation ID exist.
  • Ignore parsed operations that already exist as request items in the open project; this option is only relevant if you are updating currently open project with new OpenAPI data. If turned on, OpenAPI operations that are already part of the project as request items will be ignored during OpenAPI data parsing. If turned off, such items will be added to the list of parsed operations, but displayed in italic font.
  • Automatically include existing parsed operations to update corresponding project request items; this option is only relevant if the previous option is turned off (existing parsed operations are not ignored). If turned on, OpenAPI operations that are already part of the project as request items will be automatically marked as included.
For more information on creating projects from OpenAPI data, see the corresponding topic.

Miscellaneous

  • Open group management window after new group is created; if this option is turned on, group management window will automatically open after you create a new display or execution group from selected request items.
  • Specify WebView2 working folder; WebView2 stores its own working data on a disk and here you can specify where it should keep these files. If custom disk folder is not specifed, WebView2 will use temp folder of the current user. In any case, these WebView2 working files are deleted automatically by the application when no longer needed.

How to Copy Application Options

If you would like to copy application options to another machine, see the corresponding topic in How to section.