Development: Using Caddy to deter brute force attacks in WordPress

I really want to get my head around headers and be comfortable working with them, so, back to first principles. I refer back to a query I raised in the thread The mysterious header .

The Referer header

I go to the WP login page on the site xxx.udance.com.au/wp-login.php and see a whole bunch of stuff in the inspect screen.

I click on the first entry under the Name column and the inspect screen changes.

Under the Name column, I see a list of names of what I’m not sure? On the title row, I see six headings Headers ... Cookies. Within the body, I see several sections General, Response Headers and Request Headers. Within each of these sections, I see what look like fields and values.

My first question is 'Where do I find the field Referer header?’

header_regexp syntax

I refer to the documentation on header_regexp

The syntax is as follows:

header_regexp [<name>] <field> <regexp>

The documentation says that <name> is optional, but recommended. Why?
The <field> I figure i’lI get from somewhere on the inspect screen

The <regexp> i think I use in this instance is http(|s)://xxx\.udance\.com\.au/(wp-comments-posts|wp-login)\.php$ after reverse engineering the NginX code sample.

Putting it all together

# I think I need the 'not' version of the regexp, but I'm not sure how to get that.
@noreferrer header_regexp <name> <field>  http(|s)://xxx\.udance\.com\.au/(wp-comments-posts|wp-login)\.php$
abort @noreferrer

There are plenty of blanks to be filled in. Help!