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

[Bobbie Sellers]

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...