Updated documentation:

• What's new
• Web scenario steps
• Web monitoring example

vso Punycode is only applied to domain name, the rest which is path is URL-encoded
https://www.w3.org/International/articles/idn-and-iri/

This is a bit misleading in what's new and steps.

Specifying URLs in Unicode characters is now supported in web scenario steps. Unicode characters are automatically punycode-converted to ASCII when executing a web scenario step.

For more details, see web monitoring steps.

martins-v Changed the wording - 'Domain name' instead of 'URL'.

vso CLOSED

(1) Everything in example should be URL-encoded.

For example
Web scenario step 4
query fields are directly in URL instead of query fields.

martins-v RESOLVED

vso CLOSED

(2) Screenshots are not properly cut. for example there are half of P displayed and input fields do not have borders on the right side.

martins-v RESOLVED

vso CLOSED

(3) A little bit outdated and confusing description of variables
Here:
https://www.zabbix.com/documentation/3.4/manual/web_monitoring

It says:

Note: Variables are not URL-encoded by default. They are URL-encoded when executing the web scenario steps where these variables are used.

The first sentence is from old specification and the second one just controversial.

I suggest something more specific like:
Note: variables are automatically URL-encoded when used in form data and query fields but must be URL-encoded manually when used in raw post or directly in URL.

martins-v RESOLVED

vso CLOSED

(4) Variable description of value obtain can be improved.

Please consider.

The macros can then be referenced in the steps as {username}, {password} and {hostid}. Zabbix will automatically replace them with actual values.

Maybe it's better to say.

The macros can then be referenced in the steps as {username}, {password} and {hostid}. Zabbix will automatically replace them with actual values from previous step or scenario.

martins-v I tried to describe in a separate sentence the situation with regex variables. Also documented that step-level variables affect the following step and not the current one. Pls review. RESOLVED

vso CLOSED

(5) I don't know if it's worth mentioning in what's new that when upgrading then nothing will get automatically URL-encoded, user needs to switch from raw data to form data and move query fields from URL to separate fields.

martins-v Added to upgrade notes for 3.4. RESOLVED

vso CLOSED