...
...
...
...
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Please read the Terms of Use for Materials on ZennoLab |
Table of contents
| Expand | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
|
...
The traffic window contains all requests made by the ProjectMaker browser. Requests made using actions will also be included here. GET request , POST request , HTTP requests
...
View of the traffic window after going to https://lessons.zennolab.com/en/advanced
...
Response status (can be 200, 403, 404, 407, 503, etc.)
Request method ( GET request , POST request , PUT, DELETE, etc. )
URL where the request was made
Proxy (if used)
Time (ms) - time in milliseconds spent on request
...
The screenshot shows the server response after a POST request to https://httpbin.org/post .
...
Analysis of requests made by the browser:
to compose your own queries using actions GET request , POST request , HTTP requests
Blocking unwanted requests (using whitelists or blacklists)
...
With the help of the content policy, you can deny/allow PorjectMaker to load specific domains, URLs. You can also use regular expressions for this .
There are three possible states:
...
| Note |
|---|
Either blacklist or whitelist can be used at one time |
Without blocking - all addresses will be loaded without exception.
White list - only domains and addresses specified in the whitelist will be loaded.
Black list - all addresses will be loaded, except for those on the blacklist.
What is it for?
ProjectMaker waits for the page to fully load before executing any action. But there are situations when the page is in a state of perpetual loading or ve-e-e-ery lo-o-o-ong page load, which slows down the execution of the template. The problem may be that the browser is trying to load some script from a third-party resource, but for some reason it fails. This is where the Content Policy will help you - add the script address to the Black List , switch the policy state to the Black List, and this unloadable script will no longer spoil your life.
by blocking unwanted addresses, you can:
increase page loading speed
improve the stability of templates
reduce the amount of consumed traffic (especially important for proxies with limited traffic)
...
In the action settings (in the drop-down menu), look for Content Policy
...
Selecting the working mode.
Filtering address (domain or regular expression )
Address processing mode from point #2
Using this button, you can delete a condition (alternative option: select the desired condition and press the DELETE key on the keyboard)
Method number 3 (through the Profile window )
First, click on the Profile icon in the main window ProjectMaker(1), the current profile window will open, in it open the Browser tab(2). At the bottom of this tab, you need to activate the Content (3) . Here you can manually add new conditions for filtering requests.
...
Opening the traffic window and clicking on the above URL, you will see a large number of requests that the browser makes - to VK, Facebook, Yandex, Google, CloudFlare and other resources besides https://zennolab.com/discussion/ .
...
The screenshot shows only a small part of the requests.
Let's imagine that you need to block requests to VK, Facebook and Yandex. Additionally, you want to prevent the loading of URLs containing the word analytics (anywhere in the URL). Here's what a Content Policy action might look like to accomplish the above tasks:
...
This is how the traffic window looks like after applying the rules from the screenshot above and re-entering https://zennolab.com/discussion/
...
Useful links
...