whois | RIPE Database whois code repository | Database library

It's because when it's an array you can't compare it to a string. You can use Array#includes() though that checks if a given string is included in the array:

A potential solution.

Postgres has a jsonb store that handles unstructured data. You could use the xmltodict module via xmltodict.parse() and convert the XML to a python dict.

Than you can convert this to JSON and dump into the database.
You can query levels/depth in 2 ways:

My version:

To paraphrase the docs on scopes, the "script" scope restricts the visibility of your variable or function to the code that runs from the same script (including "child" scopes). It's similar to the concept of protected variables in other OOP languages.

Here, it was likely used to prevent you from using an "internal" function used somewhere else in the script. When it is used in a variable, it is often used to prevent tampering with variables you've defined somewhere else, or to prevent you from viewing/tampering with internal variables.

However, note that using the "script" scope doesn't work as expected when you dot-source a script since dot-sourcing loads everything into your current scope, therefore the script scope is the scope you're in when you dot-source.

Even global variables are not truly global, they are global only within the scope of their own module. There are ways to get around this restriction and share a variable between modules, if you absolutely have to, see e.g. here. It is recommended to put all global variables into a separate module and import from there, however, see the Python docs for more on this.

That said, why would you want to do this with a global variable? It's simpler and less error prone (in the sense that the restriction status would be shared between commands if global, which might lead to commands being falsely restricted) to just have check_server_restriction return True or False and then check the return value of the function something like this:

This is because the app has a vnet integration set up connecting to a Subnet delegated to Webservice/serverfarm.

Azure does not make it obvious that using delegated subnets forces an integrated app to use IPv6 and there does not appear to be a way to discover what v6 addresses may be in use. MS forum response suggests any firewall rule for a web app attached to a delegated subnet should allow ALL IPv6 addresses (!!) as a way of working around the problem.

If the Web App is VNET integrated with a subnet that has the Microsoft. Web Service Endpoint enabled, then this behavior is expected. It is by design that when the Microsoft. Web endpoint is enabled, the normal IPv4 outbound IP is no longer used. Instead, any communications will go through special tunneling using IPv6 outbound.

For adding this to a firewall, an easy way to do so is to add an allow rule by Subnet name to ensure all of its traffic is covered.

For the case where this firewall / other resource is outside of Azure / your subscription, one option would be to allow all IPv6 Azure addresses. This is because the IPv6 addresses which the subnet may use can be any of the addresses available to the Azure backplane.
Information on the IPv6 list is available for download here- Download Azure IP Ranges and Service Tags – Public Cloud from Official Microsoft Download Center

You could try this:

Check the output text - it's different between IP and domain name. Registrant Name may not be what you're looking for, change the text after reviewing the output.

After starting from ground zero, I feel I found the problem. I am now getting logon via Swagger API service (Angular 13) and the logon.cshtml Identity Razor scaffolding page.

When one properly adds the Identity scaffolding, one needs to change/review the IdentityHostingStartup.cs file. My updated IdentityHostingStartup is as follows: