What happened to autologin?

After much back and forth with support, I think we finally figured out what happened to Autofill and Autosumbit.

Since I have been using 1Password for well over a decade, I have many entries that go through redirects from the URL stored in the 1Password entry to the final "new" login page.

It seems that as soon as the site redirects to a different page than was originally asked for, 1Password gives up on autofill.

I was able to figure this out using unity.com. I created a new login entrying with unity.com and it was autofilling and autosubmitting like a champ because it used this URL:
https://id.unity.com/en/conversations/3afa00c5-408b-4ee7-b75c-5f8a942821e1018f

notice the GUID that is part of the URL. While that GUID was active and hadn't expired, unity.com would accept that as the login url. But, that GUID as since expired, resulting in a "sorry that link isn't valid" and the login entry stopped working a couple days after I created it.

I then took a look at my original unity.com login entry that takes me to the login screen but doesn't autofill. It uses https://id.unity.com as it's website url.

When I go to that url, unity then creates a new session and redirects me to a url that includes the GUID for the session, but because there was a redirect, 1Password bailed on autofilling.

To be clear, 1Password still works in that once I click on the username field, I can fill in the values and if there is only one entry for that site it will autofill. But that's not the best experience because that autofill and autosubmit have been lost due to the redirect.

I tested this on other sites too. For instance, EasyWeb is another one where autofill will never work apparently because EasyWeb starts with a URL like this: https://authentication.td.com/uap-ui/?consumer=easyweb&locale=en_CA#/uap/login
and then goes through 5 or 6 redirects, only to come back to the same URL, so I can't even update my 1password entry to the final url to get autofill working.

Is there a technical reason why autofill breaks once a redirect happens?

I can see that you might not want autofill to happen with a redirect just in case the site has been hacked and the hackers are redirecting to some harvesting site. But I could imagine that you could verify the domain and if the domain still matches the original domain and the certificate is valid for that domain, you are safe to autofill.