[sf-lug] Firefox 77.0.1 rejects sendgrid URLs.- Now Working ... IPv6 ...

Mon Jul 6 05:34:40 PDT 2020

Well, one quick-and dirty:
https://www.balug.org/
https://www.ipv4.balug.org/
https://www.ipv6.balug.org/
Those are respectively:
dual-stack (IPv4 and IPv6)
IPv4 only
IPv6 only
One can also use the handy:
https://www.balug.org/myip
https://www.ipv4.balug.org/myip
https://www.ipv6.balug.org/myip
To see one's IP address - as seen from The Internet
(e.g. after any SNAT/NAT layers one may be going through).
Also, many utilities support options to do only IPv6 (or only IPv4),
typically -6 and -4, but does vary.
E.g. ping(8), curl(1), and wget(1) all support -4 and -6 options.

So ...
$ curl -4 -I  
'https://u1584542.ct.sendgrid.net/ss/c/atcYNHk4Eh2YdGnwBh-YDNW_UEVavj84loUzOxRfMJv_zk85Z5k_bK_2c8w083WVPtJyswVJDPeA6bC07ZVNq9fUT_Q7eVj-nMX_7MPYCfIsdCvsTxCkLKOft3UuXvObt9g1ujsfAOw0m2umHrNiRzDpilzWYyYJPqEn3BMrQKVJjMkNtRqM2dSQGSyl4etQLpysfFHnXkguNvU91AQLNc22LGk2ZMWdbMi-nBqIlFv4O1zyK468iimXB2fN2o_AW0ijnlq5o19LriYU59VdpJs8iqEtnIfzOAcxVvSpo0-yB-HvGS0SftuABbt56LX4z1o2mK4-ww0SiPLk-F86vCPMjFSuSevJrXFemJxjVx6UNOWf2aYkx0QxGgJdYh8U/32i/qhteIEf1Q42lkA0z0liS1w/h0/e3-fC4qXuJ8Pak2nwzJpVv0vrRDv9uTMJwfhBu5Q8vM'
HTTP/1.1 302 Found
Server: nginx
Date: Mon, 06 Jul 2020 12:16:34 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Location:  
https://www.signherenow.org/petition/plastic-pollution/progress-america/?link_id=0&can_id=d03f7cbe2ab6c2c184ac59f4425b8e58&source=email-did-you-eat-a-credit-card-this-week-ill-explain&email_referrer=email_828804&email_subject=did-you-eat-a-credit-card-this-week-ill-explain
X-Robots-Tag: noindex, nofollow

$ curl -6 -I  
'https://u1584542.ct.sendgrid.net/ss/c/atcYNHk4Eh2YdGnwBh-YDNW_UEVavj84loUzOxRfMJv_zk85Z5k_bK_2c8w083WVPtJyswVJDPeA6bC07ZVNq9fUT_Q7eVj-nMX_7MPYCfIsdCvsTxCkLKOft3UuXvObt9g1ujsfAOw0m2umHrNiRzDpilzWYyYJPqEn3BMrQKVJjMkNtRqM2dSQGSyl4etQLpysfFHnXkguNvU91AQLNc22LGk2ZMWdbMi-nBqIlFv4O1zyK468iimXB2fN2o_AW0ijnlq5o19LriYU59VdpJs8iqEtnIfzOAcxVvSpo0-yB-HvGS0SftuABbt56LX4z1o2mK4-ww0SiPLk-F86vCPMjFSuSevJrXFemJxjVx6UNOWf2aYkx0QxGgJdYh8U/32i/qhteIEf1Q42lkA0z0liS1w/h0/e3-fC4qXuJ8Pak2nwzJpVv0vrRDv9uTMJwfhBu5Q8vM'
curl: (6) Could not resolve host: u1584542.ct.sendgrid.net
$ curl -6 -I  
'https://www.signherenow.org/petition/plastic-pollution/progress-america/?link_id=0&can_id=d03f7cbe2ab6c2c184ac59f4425b8e58&source=email-did-you-eat-a-credit-card-this-week-ill-explain&email_referrer=email_828804&email_subject=did-you-eat-a-credit-card-this-week-ill-explain'
HTTP/2 200
content-type: text/html; charset=utf-8
content-length: 12258
server: nginx
date: Mon, 06 Jul 2020 12:17:10 GMT
content-language: en
x-frame-options: SAMEORIGIN
x-content-type-options: nosniff
vary: Accept-Encoding,Cookie
x-cache: Miss from cloudfront
via: 1.1 40ddfb9607f5d49c286c41e9afdce772.cloudfront.net (CloudFront)
x-amz-cf-pop: LAX3-C3
x-amz-cf-id: sJRlIozNJIc8QoH5L8KgZi_PJLePpxjfHSz_wfgD81AVmTW34uGigg==

$ curl -4 -I  
'https://www.signherenow.org/petition/plastic-pollution/progress-america/?link_id=0&can_id=d03f7cbe2ab6c2c184ac59f4425b8e58&source=email-did-you-eat-a-credit-card-this-week-ill-explain&email_referrer=email_828804&email_subject=did-you-eat-a-credit-card-this-week-ill-explain'
HTTP/2 200
content-type: text/html; charset=utf-8
content-length: 12258
server: nginx
date: Mon, 06 Jul 2020 12:17:10 GMT
content-language: en
x-frame-options: SAMEORIGIN
x-content-type-options: nosniff
vary: Accept-Encoding,Cookie
x-cache: Hit from cloudfront
via: 1.1 d05901decd39bd339fbb13247b0f62f6.cloudfront.net (CloudFront)
x-amz-cf-pop: LAX3-C3
x-amz-cf-id: intYvTh5W1bOcrB55LvUJYsg-cjGWtqOA6oX_dYPf133X5gKMrZykA==
age: 13

$

The first URL is IPv4 only (okay, but not preferable ... whatever).
The second (the 302 redirected to) is dual stack - works with both
IPv4 and IPv6.

These days, if a client is dual stack, it should work with both.
In the earlier days of IPv6, there were "enough" (too many) broken
dual stack clients - so those clients would often fail.  So many major
players (including Google), were basically like, "Naw, we're not going
to widely deploy IPv6 on The Internet ... yet" - as the downside of many
failures, vs. the gains from functioning dual-stack (or IPv6 only)
clients ... well, for the time being was better to wait and deploy
IPv6 widely at some future date.  Well, that future date came, and
Google and many others widely deployed IPv6 - as it was generally much
more beneficial to do so, than not.  So, consequently, these days,
if you've got a dual-stack client, and it doesn't properly do IPv6
that really needs to be fixed, to avoid client caused/related
failures when dealing with IPv6 ... and likewise the network
connectivity and such, if IPv6 is being used and client given IPv6
address to use, etc.

Anyway, dual-stack clients with broken/flawed IPv6 (or network
connectivity thereof), will generally get intermittent and/or
outright failures.

Oh, and if one has a dual-stack client, disabling IPv6 is generally
not the way to go.  If need be, force IPv4, or don't
assign/take/get IPv6 addresses (notably routable), but don't shut down
the whole IPv6 stack - as much of that may be working.  Instead, work
to fix what's broken.  IPv6 becomes increasingly important as time
marches on.

I keep thinkin'/figuring too, "some day", there will be the "to die for"
"killer" IPv6 (only - likely peer-to-peer) application(s) that *everyone*
will insist upon having ... then there will be massive adoption of IPv6
(and insistence upon having it and having it working).  Maybe at some point
some IoT will drive that (IoT is pretty heavily IPv6).  In the meantime,
IPv6 continues to grow and spread and be adopted more and more ... but
it's a more slow process ... and IPv4 isn't going away anytime soon,
but alas, IPv4 IP addresses - already been exhausted, and many of
the work-arounds for that are ugly, at best.  Can't count now, in many
environments, where I've had to deal with many layers of NAT/SNAT atop
NAT/SNAT - it gets to be quite the networking nightmare - and most all
of that 'cause there's a relatively shortage of IPv4 IPs.  Can mostly
kiss that mess goodbye with IPv6.  Yeah, network troubleshooting through
multiple layers of NAT/SNAT is at best a royal pain.

> From: "Bobbie Sellers" <bliss-sf4ever at dslextreme.com>
> Subject: Re: [sf-lug] Firefox 77.0.1 rejects sendgrid URLs.- Now Working
> Date: Tue, 30 Jun 2020 23:48:39 -0700

> On 6/14/20 12:43 PM, Bobbie Sellers wrote:
>>
>>
>> On 6/10/20 10:20 PM, Michael Paoli wrote:
>>>> From: "Bobbie Sellers" <bliss-sf4ever at dslextreme.com>
>>>> Subject: Re: [sf-lug] Firefox 77.0.1 rejects sendgrid URLs.
>>>> Date: Wed, 10 Jun 2020 17:19:57 -0700
>>>
>>>>     Well this has been going on since the shift to Firefox 77.0.1
>>     And it fails to work in Firefox 67.0.4 running on Mageia in Virtual Box.
>>     Just finished about an hour's experimentation, changing Search Engines,
>> and DNS servers. Even using insecure DNS servers.
>>     And I get the same negative results but the Wiki server told me it was
>> too long and gave me the llimit and the length they accept.
>>
>>>>
>>>> This is just one example of the full URL which brings up that message.
>>>>
>>>> <https://u1584542.ct.sendgrid.net/ss/c/atcYNHk4Eh2YdGnwBh-YDNW_UEVavj84loUzOxRfMJv_zk85Z5k_bK_2c8w083WVPtJyswVJDPeA6bC07ZVNq9fUT_Q7eVj-nMX_7MPYCfIsdCvsTxCkLKOft3UuXvObt9g1ujsfAOw0m2umHrNiRzDpilzWYyYJPqEn3BMrQKVJjMkNtRqM2dSQGSyl4etQLpysfFHnXkguNvU91AQLNc22LGk2ZMWdbMi-nBqIlFv4O1zyK468iimXB2fN2o_AW0ijnlq5o19LriYU59VdpJs8iqEtnIfzOAcxVvSpo0-yB-HvGS0SftuABbt56LX4z1o2mK4-ww0SiPLk-F86vCPMjFSuSevJrXFemJxjVx6UNOWf2aYkx0QxGgJdYh8U/32i/qhteIEf1Q42lkA0z0liS1w/h0/e3-fC4qXuJ8Pak2nwzJpVv0vrRDv9uTMJwfhBu5Q8vM> All of the URLs are politically connected for petition  
>>>> signatures
>>>
>>> Seems to work fine for me:
>>> $ curl -I  
>>> 'https://u1584542.ct.sendgrid.net/ss/c/atcYNHk4Eh2YdGnwBh-YDNW_UEVavj84loUzOxRfMJv_zk85Z5k_bK_2c8w083WVPtJyswVJDPeA6bC07ZVNq9fUT_Q7eVj-nMX_7MPYCfIsdCvsTxCkLKOft3UuXvObt9g1ujsfAOw0m2umHrNiRzDpilzWYyYJPqEn3BMrQKVJjMkNtRqM2dSQGSyl4etQLpysfFHnXkguNvU91AQLNc22LGk2ZMWdbMi-nBqIlFv4O1zyK468iimXB2fN2o_AW0ijnlq5o19LriYU59VdpJs8iqEtnIfzOAcxVvSpo0-yB-HvGS0SftuABbt56LX4z1o2mK4-ww0SiPLk-F86vCPMjFSuSevJrXFemJxjVx6UNOWf2aYkx0QxGgJdYh8U/32i/qhteIEf1Q42lkA0z0liS1w/h0/e3-fC4qXuJ8Pak2nwzJpVv0vrRDv9uTMJwfhBu5Q8vM'
>>> HTTP/1.1 302 Found
>>> Server: nginx
>>> Date: Thu, 11 Jun 2020 05:15:20 GMT
>>> Content-Type: text/html; charset=utf-8
>>> Connection: keep-alive
>>> Location:  
>>> https://www.signherenow.org/petition/plastic-pollution/progress-america/?link_id=0&can_id=d03f7cbe2ab6c2c184ac59f4425b8e58&source=email-did-you-eat-a-credit-card-this-week-ill-explain&email_referrer=email_828804&email_subject=did-you-eat-a-credit-card-this-week-ill-explain
>>> X-Robots-Tag: noindex, nofollow
>>>
>>> $ curl -I  
>>> 'https://www.signherenow.org/petition/plastic-pollution/progress-america/?link_id=0&can_id=d03f7cbe2ab6c2c184ac59f4425b8e58&source=email-did-you-eat-a-credit-card-this-week-ill-explain&email_referrer=email_828804&email_subject=did-you-eat-a-credit-card-this-week-ill-explain'
>>> HTTP/2 200
>>> content-type: text/html; charset=utf-8
>>> content-length: 12258
>>> server: nginx
>>> date: Thu, 11 Jun 2020 05:15:57 GMT
>>> content-language: en
>>> x-frame-options: SAMEORIGIN
>>> x-content-type-options: nosniff
>>> vary: Accept-Encoding,Cookie
>>> x-cache: Miss from cloudfront
>>> via: 1.1 45645ff3269a2b885ffa1653e827d0f7.cloudfront.net (CloudFront)
>>> x-amz-cf-pop: SFO20-C1
>>> x-amz-cf-id: 7ZCnl7c_YPVincYASVzE1I6TbwgBg2Mj1aNg57sDOGGHUzVoklcIKA==
>>>
>>> $
>>> But I'm not using Firefox 77.0.1 - have you compared to other Firefox
>>> versions at the same time?
>>     So I copied the Location: you show above and of course it went  
>> right to that particular site but that means i would have to run
>> every URL thru "curl  -I " to get the location.
>>
>>     I still wonder what is going wrong here.
>>     I think I will ask DSLextreme tech support when I can think a  
>> bit straighter.
>>
>>     Bobbie Sellers
>>
>
>     Well it took me to the end of the month but I finally exhausted  
> all other possibilities
> On the PCLinux Forum there was a thread about what was wrong with  
> Firefox and what
> could replace it.  Suggested were Vivaldi, SeaMonkey, and Brave.
>
> Well I tried out all the suggested browsers this afternoon and some  
> complained of a
> overly long URL but none of them did any better but I think it was  
> SeaMonkey browser
>  which gave me a reference which i looked up,  and found a long  
> string of similar
> complaints and failures of solutions.
>
> Right near the bottom of the list was the answer!
>
> The IPv6, if i have the right term, is was not being properly  
> processed by the service provider.
> I went to the ISP and sent a note to Tech Support and they replied  
> with the ticket number
> very shortly.  Later I decided to try again and now the long URLs  
> work very well on Firefox
>
> But looking up the correct term IPv6 I spotted a site that claimed  
> to test IPv6 compatibility
> <http://test-ipv6.com/>
>
> This is what it told me:
>
>     Your IPv4 address on the public Internet appears to be 107.223.11.106
>      Your IPv6 address on the public Internet appears to be  
> 2600:1700:f1b1:5a90:eef4:bbff:fe71:4bde
>      Your Internet Service Provider (ISP) appears to be ATT-INTERNET4
>     You appear to be able to browse the IPv4 Internet only. You will  
> not be able to reach IPv6-only sites.
>      HTTPS support is now available on this site. [more info]
>      IPv6 connections work, but connections using DNS names do not  
> use IPv6. For some reason, your browser or your OS is not doing IPv6  
> DNS 'AAAA' lookups. [more info]
>     Your DNS server (possibly run by your ISP) appears to have IPv6  
> Internet access.
> Checked out more info link and found suggestions to turn on the IPV6  
> compatibility
> in browser going to  a about:config where you can list all the  
> configurations that
> are setup,  Or you can search as I did on the IPv6 where it had the  
> IPv6 disabled
> and make it false.  Where upon your result will change.
>     On my first pass thru http://test-ipv6,com I passed none of 10  
> tests after the
> adjustment to the config file I passed 10 or 10 tests for readiness  
> to a forced switch
> to IPv6.
>
>
>     bliss up to late playing angband...