Issue Tracker Guidelines

  • You file new Issues with the New issue entry in the main menu
  • Give enough context and version information
  • Preferably, provide a test case that isolates the issue. This helps tremendously in tracking down the cause. Often, 90% of the work is reproducing the issue.
  • If your issue was closed or rejected, do not file a new one:
    • You can still comment on a closed/rejected issue.
    • You can open a topic on the forum and discuss the issue with other users.
  • File one issue for each Bug/Feature/Request you have (do not combine them)
    • Negative Example: #2856

How to create a HAR file

When debugging a (usually network related) issue that's difficult to reproduce, a Wt developer may ask you to provide a HAR file to help with debugging. HAR (HTTP archive) files contain a full log of HTTP requests and responses. Many browsers support creating these HAR files. This section explains how to do this for several common browsers.

NOTE: HAR files may contain sensitive information, so you should make sure that when you reproduce the issue, you don't send or receive any sensitive info. You could also opt to send the HAR file to the developer directly.

Microsoft Edge

Open the developer tools with F12, and browse to the network tab. Perform the steps necessary to reproduce the issue (preferably start with a fresh instance). Now, you can save the log as a HAR file with Ctrl+S (or clicking the floppy disk (💾) icon).

Firefox

Open the network tab (Ctrl+Shift+Q or open menu -> Developer -> Network). Perform the steps necessary to reproduce the issue (preferably start with a fresh instance). Now, you can save the log as a HAR file with right click -> Save All As HAR.

Chrome

Open developer tools (F12, Ctrl+Shift+I, or open menu -> More tools -> Developer tools). Perform the steps necessary to reproduce the issue (preferable start with a fresh instance). Now you can save the log as a HAR file with right click -> Save as HAR with Content.