Tags: as desired, perhaps something descriptive such as http-received
Configuring the Action
The Global Filter's Action setting determines what will happen to the request.
To block the request completely, choose a blocking Action (perhaps the default Global filter block Action).
To redirect the HTTP request to HTTPS, you can select the default https redirect Action (shown below). If you choose to edit this Action or use a different one, ensure that the selected Action has the same Status code, and the same setting for the location header.
Configuring the Rule list
Within the Rule list, select +New Entry. Populate the new entry with:
Category set toTag
Match set to scheme:http
Whatever Annotation you wish.
At this point, the Global Filter should look something like this:
Configuring the Scope
By following the steps above, you have a Global Filter that will block or redirect HTTP traffic globally, throughout the entire planet.
If instead you only want to apply this Global Filter to certain paths within the planet, you must create one or more additional entries in the Rule list. Each should have:
Category set toPath
Match set to a regex describing the path
Whatever Annotation you wish.
Create as many entries as necessary to include all the desired paths.
Note that these entries should all be within the same section as the first Tag entry. (If instead you selected +New section, and the entries are now in separate sections, ensure that the relation between them is set to Relation: AND.)
Saving and Publishing
When you have completed the steps above, the Global Filter has been created.