1. Open Developer Tools: Press F12 or right-click the page and select “Inspect”.

2. Network Tab: Click on “Network” to view network activity.

3. Perform Upload: Upload a file as usual.

4. Identify POST Request: Look for a POST request in the network list; this is the upload action.

5. Examine Details: Click the POST request to see its headers and payload, revealing the upload URL and parameters.

This method helps you pinpoint the exact URL and data structure for file uploads, enabling API simulations.

1. Restart Windows
2. Re-install HttpWatch

If you still have problems please email [email protected] with details of the versions of HttpWatch and Chrome that you are using.

I noticed that the plugin is not active at startup.
Although after clicking on it, it becomes active.

And I want to note - the first launch after a “clean” installation of HttpWatch and the Edge plugin was successful. Are there any requirements for the user rights under which the tests are carried out, and also was ntpwatch installed and configured?
Also on another computers test works fine.

Please directly contact [email protected] and we can advise you whether your license will work with the latest version of HttpWatch.

RID not found in network event policyUpdated
(Saved dump file to C:\Users\AUTOTE~1\AppData\Local\Temp\HttpWatchForChromiumx64.exe.12016.2004.dmp)
NativeChromiumPort::ReadMessagesFromChromiumOnStdInThread
Version: 14.0.25
Exception type: std::exception

While using HttpWatch with Edge with lower version (120, 126, 117) - all going good.

Need help solving this problem.

Regards

Simon Perkins

The message is “An error occurred with HttpWatch - Access to the specified native messaging host is forbidden.” can anyone help me.

Regards

This may be useful for others, what I have found in testing is that is If I set Httpwatch to automatically record / save on exit in the IE11 addin / extension it does record the Edge IEmode launched sites / sessions. I can’t open the Httpwatch window during this session / change setting on the fly but if I need to set anything specific I can change setting in an IE11 window first .

As my application flow goes back and forwards to edge native and IE mode for compatibility it does give me two sets of traces (one edge one IE11) and isn’t ideal, but works for me… and if your whole app / site runs in IEmode it isn’t a problem.

When IE11 goes EoL / gets removed in June 2022 this won’t work (probably…) but may help people work with and investigate issues in IEmode until then.

Thanks,

K

Although Edge’s IE Mode supports Browser Helper Objects (BHO) it does not support IE extensions. The HttpWatch support for IE requires both the use of a BHO and an IE extension.

Unfortunately, this means that HttpWatch will only work in IE 11 - not Edge’s IE mode.

Does Httpwatch support or can it be made to capture a trace in Edge IEmode?

I get the below error launching from the edge toolbar:

and the right click IE option within an IEmode tab does nothing.

Microsoft say IE Mode will support the following functionalities:

• All document modes and enterprise modes
• ActiveX controls (such as Java or Silverlight). Note: Silverlight reaches the end of support on October 12, 2021.
• Browser Helper Objects
• Internet Explorer settings and group policies that affect security zone settings and Protected Mode
• F12 developer tools for IE, when launched with IEChooser
• Microsoft Edge extensions (Extensions that interact with the IE page content directly are not supported.)

I assume that the edge HTTPwatch extention is not allowed to interact with the page from the toolbar / Edge extention button.

but I had hoped it may have launched the IE11 HTTPwatch BHO object from the right click menu option instead.

Should this work? If so any idea’s of the required config? If it doesn’t work now is it in any roadmap to support it?

Many thanks in advance

The HW3001 warning occurred because the request failed with ERROR_INTERNET_NAME_NOT_RESOLVED. Usually this happens if the DNS lookup for the hostname (i.e. fonts.googleapis.com) fails. The hostname is valid and available in public DNS servers so this may have been caused by the local network having its own custom DNS server or there is some kind of security software installed that is blocking HTTP requests.

Finally, the POST request to http://localhost:58987 looks like some kind of debugging code has been left in the web page. With the Profession Edition of HttpWatch you could look at the response to this request and search for the HTML/JavaScript code that triggered it.

If you would like more detail and are happy to share the HWL file please send a copy to [email protected] . We can provide more feedback and convert it into the Pro format so that you can see all the data yourself.

Question-1) HW2001 & HW3001 - What could be causing this error?
Question-2) What is http:/localhost:58987 in the picture below? *
The host address I specify and use is http:/localhost:70/ .*
How can I resolve this error?

HW2001 : The request used insecure HTTP. This will compromise security and trigger browser security warnings.
HW3001 : The request retruned a HTTP status code failure or caused an interanl brower error. Failing requests may prevent a web page functioning correctly and cause performance problems.

The URL you mentioned requires a login. However, we do have a file upload example on our web site:

https://www.httpwatch.com/httpgallery/methods/#showExample6c

If you start recording in Chrome with HttpWatch on this page and then click on the Submit button you’ll see a POST request. For file uploads the request body uses the mime type multi-part/form-data:

If you then click on the ‘View As’ menu and select ‘Source Text’ you’ll see the format of the request body using multi-part/form-data to separate values:

Unfortunately, the debugging interface to Chrome always omits the actual file contents. The picture below shows where the file contents should appear:

If you use HttpWatch in Internet Explorer there is no such restriction and you can see the full contents of the request body.

https://blog.httpwatch.com/2021/08/06/how-to-automatically-install-and-enable-a-chrome-extension/

Software\Policies\Google\Chrome\NativeMessagingAllowlist\1 = com.httpwatch.chrome.extension

and for Edge use com.httpwatch.edge.extension (see Edge NativeMessaging Policies):

SOFTWARE\Policies\Microsoft\Edge\NativeMessagingAllowlist\1 = com.httpwatch.edge.extension

Software\Policies\Google\Chrome\NativeMessagingBlocklist\1 = '*'

(See Chrome Enterprise Policy List & Management | Documentation )

When attempting to use HttpWatch this causes the following error:

What value should I add to the NativeMessagingAllowlist to enable HttpWatch for Native Messaging?

The Elapsed Time is the time interval from the start of the first request to the end of the last request on a page (see help on the network tab). However, during this time several requests may overlap meaning that you can’t simply add their durations together to find the elapsed time for the whole page. The time chart below has a highlighted group of requests that are running concurrently.

Why is this? Shouldn’t the sum of the network times of each request on the page be equal to the Elapsed Time?

https://help.httpwatch.com/silent_install.html

C:\Program Files (x86)\HttpWatch\HttpWatchApiPro.dll (32 bit)
C:\Program Files (x86)\HttpWatch\HttpWatchApiProx64.dll (64 bit)

One way is to use COM form Java is with com4J:

https://com4j.kohsuke.org/

These slides have some details of how to do this with HttpWatch:

Alternatively, you could consider setting up automatic recording so that a log file is saved automatically at regular intervals from all windows, tabs and popups in Chrome:

https://help.httpwatch.com/options_recording.html

Here you can:

• Ask questions about using HttpWatch
• Share things you have done with HttpWatch
• Request or vote on new features
• Keep up to date with news

Please note that there is also comprehensive documentation on using and automating HttpWatch.

Bug reports should be emailed direct .