When I try to access https://www.haaretz.com/ I get this:

---------------------------
Error 403 Forbidden

Forbidden
Error 54113

Details: cache-ewr18128-EWR 1698434873 3591930481

Varnish cache server
---------------------------

However in Google Chrome the page loads without problem.

Why Firefox doesn't load it?

emfril,

> When I try to access https://www.haaretz.com/ I get this:
....
> Why Firefox doesn't load it?

Hmmm?

You might want to be a bit more specific about that, as my (ancient) version
of FF doesn't seem to have any problems with it.

Regards,
Rudy Wieser

On Fri, 3 Nov 2023 15:17:52 -0400, emfril wrote:
> When I try to access https://www.haaretz.com/ I get this:
>
> ---------------------------
> Error 403 Forbidden
>
> Forbidden
> Error 54113
>
> Details: cache-ewr18128-EWR 1698434873 3591930481
>
> Varnish cache server
> ---------------------------
>
> However in Google Chrome the page loads without problem.
>
> Why Firefox doesn't load it?
>

It loads for me, in English. Firefox 119.0, Windows 10.

--
Stan Brown, Tehachapi, California, USA https://BrownMath.com/
Shikata ga nai...

emfril <emfril@gmail.com> wrote:

>When I try to access https://www.haaretz.com/ I get this:

>---------------------------
>Error 403 Forbidden

>Forbidden
>Error 54113

>Details: cache-ewr18128-EWR 1698434873 3591930481

>Varnish cache server
>---------------------------

>However in Google Chrome the page loads without problem.

>Why Firefox doesn't load it?

I cannot recreate that error.

What does it matter? 403 is temporary. Who cares?

As you didn't tell us that you dumped the cache and reloaded the page
with Chrome, I'll guess that's the reason.

On 11/3/2023 12:36 PM, Stan Brown wrote:
> On Fri, 3 Nov 2023 15:17:52 -0400, emfril wrote:
>> When I try to access https://www.haaretz.com/ I get this:
>>
>> ---------------------------
>> Error 403 Forbidden
>>
>> Forbidden
>> Error 54113
>>
>> Details: cache-ewr18128-EWR 1698434873 3591930481
>>
>> Varnish cache server
>> ---------------------------
>>
>> However in Google Chrome the page loads without problem.
>>
>> Why Firefox doesn't load it?
>>
>
> It loads for me, in English. Firefox 119.0, Windows 10.
>

Ditto with SeaMonkey 2.53.16 under Windows 7.

--
David E. Ross
<http://www.rosde.com/>

X (previously known as Twitter) is the place where truth goes to die.

On 03.11.23 20:17, emfril wrote:
> When I try to access https://www.haaretz.com/ I get this:
>
> ---------------------------
> Error 403 Forbidden
>
> Forbidden
> Error 54113
>
> Details: cache-ewr18128-EWR 1698434873 3591930481
>
> Varnish cache server
> ---------------------------
>
> However in Google Chrome the page loads without problem.
>
> Why Firefox doesn't load it?

My 119.0 is loading that from the website within milliseconds.
Are you using a provider with DNS-censorship?

--
Gutta cavat lapidem (Ovid)

On 03.11.23 21:24, Jörg Lorenz wrote:
> On 03.11.23 20:17, emfril wrote:
>> When I try to access https://www.haaretz.com/ I get this:
>>
>> ---------------------------
>> Error 403 Forbidden
>>
>> Forbidden
>> Error 54113
>>
>> Details: cache-ewr18128-EWR 1698434873 3591930481
>>
>> Varnish cache server
>> ---------------------------
>>
>> However in Google Chrome the page loads without problem.
>>
>> Why Firefox doesn't load it?
>
> My 119.0 is loading that from the website within milliseconds.
> Are you using a provider with DNS-censorship?

Use this DNS over https:

https://unicast.uncensoreddns.org/dns-query

--
Gutta cavat lapidem (Ovid)

On Fri, 3 Nov 2023 12:36:58 -0700, Stan Brown
<the_stan_brown@fastmail.fm> wrote:

>On Fri, 3 Nov 2023 15:17:52 -0400, emfril wrote:
>> When I try to access https://www.haaretz.com/ I get this:
>>
>> ---------------------------
>> Error 403 Forbidden
>>
>> Forbidden
>> Error 54113
>>
>> Details: cache-ewr18128-EWR 1698434873 3591930481
>>
>> Varnish cache server
>> ---------------------------
>>
>> However in Google Chrome the page loads without problem.
>>
>> Why Firefox doesn't load it?
>>
>
>It loads for me, in English. Firefox 119.0, Windows 10.

No problem with Firefox 115.4.0.esr using Windows 7

On Fri, 3 Nov 2023 15:17:52 -0400, emfril <emfril@gmail.com> wrote:

>When I try to access https://www.haaretz.com/ I get this:
>
>---------------------------
>Error 403 Forbidden
>
>Forbidden
>Error 54113
>
>Details: cache-ewr18128-EWR 1698434873 3591930481
>
>Varnish cache server
>---------------------------
>
>However in Google Chrome the page loads without problem.
>
>Why Firefox doesn't load it?

Might as well join the crowd... it works for me Ffox 119.0 Win 11.

emfril <emfril@gmail.com> wrote:

> When I try to access https://www.haaretz.com/ I get this:
>
> ---------------------------
> Error 403 Forbidden
>
> Forbidden
> Error 54113
>
> Details: cache-ewr18128-EWR 1698434873 3591930481
>
> Varnish cache server
> ---------------------------
>
> However in Google Chrome the page loads without problem.
>
> Why Firefox doesn't load it?

Works for me in FF 119.0 on Windows 10 Home.

https://www.allconnect.com/blog/403-forbidden-error-explained

Servers need maintenance, too. Perhaps a web page or resource was
getting redefined, but a pointer on the old copy, or your locally cached
copy, still referenced an old resource that was no longer available or
at its old location. Try flushing FF's locally cached data, and retry.

Do you have geo.enabled = false in about:config? If not, perhaps you
are in a region that is restricted from accessing the site's content. I
know, in the past, I'd try to see some bbc.co.uk pages, but was blocked
from the site, because either geolocation services in FF, or the
geolocation for my IP address, was in their lockout list. I go
elsewhere when that happens. Rarely is the information available at
only one web site.

Some folks use VPNs to use an exit node from the VPN that is in an
acceptable region for a site. However, tis likely your WAN-side IP
address is the same whether you use FF or Chrome assuming your testing
was on the same host and inside the same network.

If still blocked, did you try disabling all add-ons you installed into
FF (likely you don't have the same set of add-ons, if any, in Chrome),
flushling all FF's locally cached data, and reload FF to test the site
again?

I've seen where a site will change what it stores in its cookies on your
computer. They had one structure, changed it to a new data set in their
cookies, but their old cookies you kept won't work with their site
anymore. Again, flushing all locally cached data would also wipe any
cookies you kept on your computer. FF and Chrome don't share cookie
files.

On 03/11/2023 19:17, emfril wrote:
>
>
> Why Firefox doesn't load it?

It could be because that website is reporting about genocide in Gaza.
Some country has enlisted conscripts to kill as many Palestinians as
possible. They have killed 9.000 so far and the number is climbing.

On Fri, 3 Nov 2023 22:30:00 +0000, Hassan Nasrallah
<invalid@invalid.net> wrote:

>On 03/11/2023 19:17, emfril wrote:
>>
>>
>> Why Firefox doesn't load it?
>
>It could be because that website is reporting about genocide in Gaza.
>Some country has enlisted conscripts to kill as many Palestinians as
>possible. They have killed 9.000 so far and the number is climbing.

HAMAS PROBABLY

KenW

emfril wrote:

> Why Firefox doesn't load it?

It's not that firefox doesn't want to load it, just that their server
doesn't want to send it to you ...

"emfril" <emfril@gmail.com> wrote

| When I try to access https://www.haaretz.com/ I get this:
| | ---------------------------
| Error 403 Forbidden
|

It's hard to know. It loads fine for me in New Moon. I didn't
try Firefox. I don't have Chrome. A 403 will be happening at
page load, maybe through PHP, so it's hard to know the actual
cause. I often get them at Home Depot or Lowes, which
I'm guessing is because they may try to block deep linking,
or it may just be an aggressive way of demanding script enabled.
Or maybe they're just incompetent.

Haaretz is an interesting website. I'd never seen it before.
They seem to be level-headed and informative, while the US
mainstream media are coming across like the Netanyahoo Times.

Checking the articles now I see that the whole domain
is a dummy website. It's subscription-only -- essentially
a private, members-only business. So that might also
play into the 403.

Newyana2 wrote:

> Checking the articles now I see that the whole domain is a dummy
> website. It's subscription-only -- essentially a private,
> members-only business. So that might also play into the 403.

Seems unfair to call it "a dummy website". It's a news site like many
others, which lets you read headlines and an opening paragraph or two
for free, then requires payment for anything more. It's like standing
in a newsagent's shop and reading the front page without buying the
paper. I always regarded it as a bit rude of people who thumb through
the whole paper and then put it back.

Am 04.11.23 um 13:47 schrieb Newyana2:
> "emfril" <emfril@gmail.com> wrote
>
> | When I try to access https://www.haaretz.com/ I get this:
> |
> | ---------------------------
> | Error 403 Forbidden
> |
>
> It's hard to know. It loads fine for me in New Moon. I didn't
> try Firefox. I don't have Chrome. A 403 will be happening at
> page load, maybe through PHP, so it's hard to know the actual
> cause. I often get them at Home Depot or Lowes, which
> I'm guessing is because they may try to block deep linking,
> or it may just be an aggressive way of demanding script enabled.
> Or maybe they're just incompetent.
>
> Haaretz is an interesting website. I'd never seen it before.
> They seem to be level-headed and informative, while the US
> mainstream media are coming across like the Netanyahoo Times.

Idiot.

--
Gutta cavat lapidem (Ovid)

Am 04.11.23 um 13:57 schrieb Newyana2:
> Checking the articles now I see that the whole domain
> is a dummy website. It's subscription-only -- essentially
> a private, members-only business. So that might also
> play into the 403.

Americans are naïve. They always were. And they still are.

--
Gutta cavat lapidem (Ovid)

Hassan Nasrallah <invalid@invalid.net> wrote:
>On 03/11/2023 19:17, emfril wrote:

>>Why Firefox doesn't load it?

>It could be because that website is reporting about genocide in Gaza.
>Some country has enlisted conscripts to kill as many Palestinians as
>possible. They have killed 9.000 so far and the number is climbing.

Our constantly-morphing troll is claiming to be the head of Hezbollah,
the Iranian proxy in Lebanon.

Yeah. The Haaretz Web site was blocked because the newspaper is anti-Israel
and sympathetic toward Hamas in the war that Hamas started.

Oh, wait, maybe they're not:

Hamas Tried to Sneak Its Fighters Out of Gaza With Wounded and Foreign
Nationals, U.S. Official Says

U.S. and Egyptian officials found that a third of the names selected to
exit Gaza via Rafah crossing into Egypt were Hamas fighters, none of
whom were among the 76 wounded Palestinians eventually evacuated
by Ben Samuels
Nov 4, 2023 1:25 pm IST
https://www.haaretz.com/israel-news/2023-11-04/ty-article/.premium/u-s-official-hamas-tried-to-sneak-out-fighters-with-wounded-and-foreign-nationals/0000018b-9a03-db71-a7df-ffcf50a00000

So, once again, Hamas used human shields and therefore committed yet
another war crime. Hamas was tempting the Israelis into attacking their
fighters which would have also resulting in more civilian deaths.

That strongly suggests that Israel told the truth about why they attacked
ambulances at that hospital in Gaza City yesterday.

On 2023-11-03 18:15, VanguardLH wrote:
> emfril <emfril@gmail.com> wrote:
>
>> When I try to access https://www.haaretz.com/ I get this:
>>
>> ---------------------------
>> Error 403 Forbidden
>>
>> Forbidden
>> Error 54113
>>
>> Details: cache-ewr18128-EWR 1698434873 3591930481
>>
>> Varnish cache server
>> ---------------------------
>>
>> However in Google Chrome the page loads without problem.
>>
>> Why Firefox doesn't load it?
>
> Works for me in FF 119.0 on Windows 10 Home.
>
> https://www.allconnect.com/blog/403-forbidden-error-explained
>
> Servers need maintenance, too. Perhaps a web page or resource was
> getting redefined, but a pointer on the old copy, or your locally cached
> copy, still referenced an old resource that was no longer available or
> at its old location. Try flushing FF's locally cached data, and retry.
>
> Do you have geo.enabled = false in about:config? If not, perhaps you
> are in a region that is restricted from accessing the site's content. I
> know, in the past, I'd try to see some bbc.co.uk pages, but was blocked
> from the site, because either geolocation services in FF, or the
> geolocation for my IP address, was in their lockout list. I go
> elsewhere when that happens. Rarely is the information available at
> only one web site.
>
> Some folks use VPNs to use an exit node from the VPN that is in an
> acceptable region for a site. However, tis likely your WAN-side IP
> address is the same whether you use FF or Chrome assuming your testing
> was on the same host and inside the same network.
>
> If still blocked, did you try disabling all add-ons you installed into
> FF (likely you don't have the same set of add-ons, if any, in Chrome),
> flushling all FF's locally cached data, and reload FF to test the site
> again?
>
> I've seen where a site will change what it stores in its cookies on your
> computer. They had one structure, changed it to a new data set in their
> cookies, but their old cookies you kept won't work with their site
> anymore. Again, flushing all locally cached data would also wipe any
> cookies you kept on your computer. FF and Chrome don't share cookie
> files.

The problem was the Ad-block extension. When I turned it off the
website loaded, Then I turned it on again and it is still
loading. Thanks everybody for letting me know that the problem
was not with Firefox.

BTW, how do you empty cache now? That was something that in the
past I would find useful sometimes, but now I can't find a
command in the menu bar...

emfril <emfril@gmail.com> wrote:

>. . .

>BTW, how do you empty cache now? That was something that in the
>past I would find useful sometimes, but now I can't find a
>command in the menu bar...

about:preferences > Privacy & Security > History > Clear History

You'll see the Clear Recent History popup with various choices.

To reload a Web page from the server and not the cache

Shft+Ctrl+R

"Adam H. Kerman" <ahk@chinet.com> wrote:

> emfril <emfril@gmail.com> wrote:
>
>>. . .
>
>>BTW, how do you empty cache now? That was something that in the
>>past I would find useful sometimes, but now I can't find a
>>command in the menu bar...
>
> about:preferences > Privacy & Security > History > Clear History
>
> You'll see the Clear Recent History popup with various choices.
>
> To reload a Web page from the server and not the cache
>
> Shft+Ctrl+R

Also under settings (3-bar menu icon) -> History -> Clear recent history

Or using a shortcut key: Ctrl+Shift+Del
https://support.mozilla.org/en-US/kb/keyboard-shortcuts-perform-firefox-tasks-quickly#w_history
History section

There are probably other ways to get at and clear history, or just some
of the types of locally stored data. I configured FF to purge all
locally cached data on its exit: about:preferences#privacy -> History,
enable "Clear history when Firefox closes", click Settings, I've got all
types selected for purge.

Unless you have a need otherwise, choose all local data types. However,
if you ever saved settings on a per-site basis, clearing "Site settings"
will lose those. "Offline website data "(aka DOM Storage aka Web
Storage) removes super-cookies that can be far more huge than using .txt
files as cookies.

https://en.wikipedia.org/wiki/Web_storage

DOM Storage is how a site can store a hell of alot more info than for
cookie files. Many use it for session storage: upon returning to a
site, you start where you left off, like when adding items to a cart.
Instead of having every keypress sent to the server to check if you
entered a valid character into crossword puzzle, they download a lookup
table into your web browser's DOM Storage, and the page script uses that
local data when filling out their crossword web page. Online games will
use DOM Storage for local copy of objects, textures, and other resources
that would far faster to get locally than having the server deliver them
when needed.