Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #181780 > unrolled thread

why can't I visit this web site

Back to article view | Back to linux.debian.user

Contents

  why can't I visit this web site Long Wind <longwind2009@gmail.com> - 2017-06-06 02:20 +0200
    Re: why can't I visit this web site Richard Owlett <rowlett@cloud85.net> - 2017-06-06 02:40 +0200
      Re: why can't I visit this web site <tomas@tuxteam.de> - 2017-06-06 10:10 +0200
        Re: why can't I visit this web site Long Wind <longwind2009@gmail.com> - 2017-06-06 14:10 +0200
          Re: why can't I visit this web site "Thomas Schmitt" <scdbackup@gmx.net> - 2017-06-06 14:40 +0200
          Re: why can't I visit this web site <tomas@tuxteam.de> - 2017-06-06 14:40 +0200
            Re: why can't I visit this web site Greg Wooledge <wooledg@eeg.ccf.org> - 2017-06-06 15:00 +0200
              Re: why can't I visit this web site <tomas@tuxteam.de> - 2017-06-06 15:20 +0200
              Re: why can't I visit this web site Richard Owlett <rowlett@cloud85.net> - 2017-06-06 15:50 +0200
          Re: why can't I visit this web site Joe <joe@jretrading.com> - 2017-06-06 14:50 +0200
    Re: why can't I visit this web site Ben Finney <bignose@debian.org> - 2017-06-06 02:40 +0200
      Re: why can't I visit this web site Lisi Reisz <lisi.reisz@gmail.com> - 2017-06-06 09:50 +0200
        Re: why can't I visit this web site rhkramer@gmail.com - 2017-06-06 14:50 +0200
      Re: why can't I visit this web site Jude DaShiell <jdashiel@panix.com> - 2017-06-06 18:20 +0200
        Re: why can't I visit this web site Greg Wooledge <wooledg@eeg.ccf.org> - 2017-06-06 18:40 +0200
        Re: why can't I visit this web site Dan Purgert <dan@djph.net> - 2017-06-06 18:50 +0200
    Re: why can't I visit this web site Long Wind <longwind2009@gmail.com> - 2017-06-06 03:40 +0200
      Re: why can't I visit this web site Ben Finney <bignose@debian.org> - 2017-06-06 04:50 +0200
      Re: why can't I visit this web site SDA <marathon.durandal@gmail.com> - 2017-06-06 23:20 +0200
    Re: why can't I visit this web site rhkramer@gmail.com - 2017-06-06 14:50 +0200
      Re: why can't I visit this web site Ken Heard <kenslists@teksavvy.com> - 2017-06-06 23:20 +0200
    Re: why can't I visit this web site Charlie S <taoquester@gmail.com> - 2017-06-07 01:40 +0200
      Re: why can't I visit this web site Long Wind <longwind2009@gmail.com> - 2017-06-07 04:20 +0200
        Re: why can't I visit this web site Paul Scott <waterhorse@ultrasw.com> - 2017-06-07 07:40 +0200
      Re: why can't I visit this web site Long Wind <longwind2009@gmail.com> - 2017-06-07 05:50 +0200

Page 1 of 2  [1] 2  Next page →

#181780 — why can't I visit this web site

this is really unbelievable
I can't visit this site with jessie/iceweasel

http://www.cs.ecitic.com/

I can visit it with XP/firefox

can you help me and test the site?

[toc] | [next] | [standalone]

#181781

On 06/05/2017 07:12 PM, Long Wind wrote:
> this is really unbelievable
> I can't visit this site with jessie/iceweasel
>
> http://www.cs.ecitic.com/
>
> I can visit it with XP/firefox
>
> can you help me and test the site?
>
>

Using Stretch and SeaMonkey 2.46 with JavaScript and cookies *DISABLED*
It loads something but _displays_ nothing.
Displaying web page by using CNTRL-U reveals a VERY long single line 
containing JavaScript.

I avoid unknown sites that display nothing unless JavaScript enabled.
YMMV

[toc] | [prev] | [next] | [standalone]

#181794

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, Jun 05, 2017 at 07:38:05PM -0500, Richard Owlett wrote:
> On 06/05/2017 07:12 PM, Long Wind wrote:
> >this is really unbelievable
> >I can't visit this site with jessie/iceweasel

> Using Stretch and SeaMonkey 2.46 with JavaScript and cookies *DISABLED*
> It loads something but _displays_ nothing.
> Displaying web page by using CNTRL-U reveals a VERY long single line
> containing JavaScript.

Same here. Host resolves alright, page loads, but is Javascript-only.

> I avoid unknown sites that display nothing unless JavaScript enabled.
> YMMV

Heh. So we're at least *two* :-)

I'd go further: I consider a page which refuses to show anything when
Javascript is disabled as highly suspicious -- borderline malware.

(Yeah, I know, I know: The Internet is evolving, blah, blah. Not in
a good direction, IMO).

As Richard says: YMMV.

Cheers
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlk2YlgACgkQBcgs9XrR2kZXGwCfWaLVYbchIRK3xUPJIpGjLwzK
lv0AnAiP8av8ELCKQpfrgw3fakGTyl90
=OWZV
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#181809

i can't find options related to javascript in iceweasel/jessie

iceweasel does not support javascript?

i think iceweasel makes poor choice
XP/firefox and android' browser can visit this site

[toc] | [prev] | [next] | [standalone]

#181812

Hi,

Long Wind wrote:
> i can't find options related to javascript in iceweasel/jessie
> iceweasel does not support javascript?

It did for me by default.  I rather had to riddle how to disable it.

I go to pseudo URL
  about:config
to see a long list of adjustable properties.
When i type into the "Search" field:
  java
the second item in the now reduced list becomes
  javacript.enabled
I doubleclick to toggle between values "false" and "true".

After having gone back to the page which needs Javascript, i reload that
page to see its content ... and all the awful Javascript frippery.
(I looked up "Firlefanz" in dict.cc, "frippery" was funniest.)

As soon as possible i disable Javascript again.


Have a nice day :)

Thomas

[toc] | [prev] | [next] | [standalone]

#181814

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, Jun 06, 2017 at 08:06:30PM +0800, Long Wind wrote:
> i can't find options related to javascript in iceweasel/jessie

They have taken it out: it's "always enabled" unless you dig into
about:config.

Firefox developers have decreed that their users are too stupid
to cope with an "on/off" switch for Javascript. Sad, but true.

> iceweasel does not support javascript?

It doesn't support *disabling* javascript. It's always on.

> i think iceweasel makes poor choice

I agree (although we are talking about slightly different things :)

> XP/firefox and android' browser can visit this site

I have no idea what incompatible code "this site" uses. Or what
else is going on (perhaps some other site, which that page needs
to work, is being blocked in one but not in the other installation).

I would say the problem lies in bad javascript code in that site,
although I don't feel like debugging some random javascript code
off the 'net. It's too depressing.

Regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlk2oNUACgkQBcgs9XrR2kalLgCfcsqnvpF/Q+Tp+jnK3Jiz50a1
S2YAmQEBmTI/ASuQTwRhFrbY6bNlyPDL
=PyWm
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#181818

On Tue, Jun 06, 2017 at 02:32:21PM +0200, tomas@tuxteam.de wrote:
> On Tue, Jun 06, 2017 at 08:06:30PM +0800, Long Wind wrote:
> > iceweasel does not support javascript?
> 
> It doesn't support *disabling* javascript. It's always on.

You may want to try the NoScript extension.  It disables all Javascript
by default, and allows you to turn it on for specific domains.

https://noscript.net/

For some people, it may be too aggressive.  It depends on what web
sites you intend to use.

> Firefox developers have decreed that their users are too stupid
> to cope with an "on/off" switch for Javascript. Sad, but true.

In the last decade or so, the overall Firefox policy seems to have become
"forget whatever we used to do, let's force people to write extensions
to provide those features".  And in the last year or two, as people
started using extensions to provide the features Firefox has stripped
out, the policy has become "let's block the use of extensions".

https://support.mozilla.org/en-US/kb/add-on-signing-in-firefox

So, uh, good luck.

[toc] | [prev] | [next] | [standalone]

#181819

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, Jun 06, 2017 at 08:54:49AM -0400, Greg Wooledge wrote:
> On Tue, Jun 06, 2017 at 02:32:21PM +0200, tomas@tuxteam.de wrote:
> > On Tue, Jun 06, 2017 at 08:06:30PM +0800, Long Wind wrote:
> > > iceweasel does not support javascript?
> > 
> > It doesn't support *disabling* javascript. It's always on.
> 
> You may want to try the NoScript extension.  It disables all Javascript
> by default, and allows you to turn it on for specific domains.
> 
> https://noscript.net/
> 
> For some people, it may be too aggressive.  It depends on what web
> sites you intend to use.

I know that. I prefer something more aggressive: disabling Javascript
in about:config (and disabling quite a few other things, btw), and
using that as my default browsing profile.

Then I have a couple of other (separate) profiles for very specific
pages. Pages which don't work without javascript usually don't interest
me.

> > Firefox developers have decreed that their users are too stupid
> > to cope with an "on/off" switch for Javascript. Sad, but true.
> 
> In the last decade or so, the overall Firefox policy seems to have become
> "forget whatever we used to do, let's force people to write extensions
> to provide those features".  And in the last year or two, as people
> started using extensions to provide the features Firefox has stripped
> out, the policy has become "let's block the use of extensions".
> 
> https://support.mozilla.org/en-US/kb/add-on-signing-in-firefox
> 
> So, uh, good luck.

I know. I suppose that it's a question of perspective. I've had
discussions with Firefox people, and while they most probably
are well intentioned, their vision is very biased. For one example,
they reason that taking away the "disable javascript" switch
is based on telemetry: it causes problems for some users.

But that this keeps many beginners from experimenting and
learning, and at the same time re-inforces "web programmers"
in their use of horrific frameworks which rely on more and
more programs running client-side... that's something they
only view as a Good Thing (just think about how much Mozilla
has invested on a well-performing Javascript implementation.
Heck, the PDF viewer is written in Javascript these days:
an impressive technical feat, and many nifty tricks in
there, but... no, thanks!).

For me, it's a Bad Thing, because it makes the interface
between the service and my computer ever more obfuscated
(was: a document in an ugly, but somewhat specified language,
is: some obscure protocol which only the service provider[1]
controls, since (s)he develops server and client-side parts
in lockstep).

So thanks, but no thanks. Call me luddite if you want, but
I don't like the path things are taking. Things may have a
free license, but are becoming so obfuscated as to be effectively
non-free.

Cheers

[1] Or the service provider's framework provider (who these
   days is mostly Google or Facebook because distributed
   programming Is Hard and needs lots of resources).

- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlk2q4kACgkQBcgs9XrR2kbMNACfRiT0w10UH8ZJ9j5v5zwmkyYo
bLkAnA5ohz/dJHWcZuXUeFay48cSJ1dE
=CZNV
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#181825

On 06/06/2017 07:54 AM, Greg Wooledge wrote:
> [snip]
>
>> Firefox developers have decreed that their users are too stupid
>> to cope with an "on/off" switch for Javascript. Sad, but true.
>
> In the last decade or so, the overall Firefox policy seems to have become
> "forget whatever we used to do, let's force people to write extensions
> to provide those features".  And in the last year or two, as people
> started using extensions to provide the features Firefox has stripped
> out, the policy has become "let's block the use of extensions".
>
> https://support.mozilla.org/en-US/kb/add-on-signing-in-firefox
>
> So, uh, good luck.
>

There is SeaMonkey <https://www.seamonkey-project.org/>
I'm running their default Linux package on both Jessie and Stretch with 
Mate DE with no problems.

I abandoned Firefox and Thunderbird before abandoning WinXP ;/

[toc] | [prev] | [next] | [standalone]

#181817

On Tue, 6 Jun 2017 20:06:30 +0800
Long Wind <longwind2009@gmail.com> wrote:

> i can't find options related to javascript in iceweasel/jessie
> 

In about:config. Type that into the address bar, then in the Search
box, type javascript. The global disable is called javascript.enable.

More commonly, firefox/iceweasel users use NoScript or other selective
javascript enabler.

> iceweasel does not support javascript?

Every version that I've seen does. It has always been Firefox by
another name, but usually not the current version.
> 
> i think iceweasel makes poor choice
> XP/firefox and android' browser can visit this site
> 

And many web developers don't bother to test Firefox versions, because
obviously, people only use Microsoft web browsers. Two hours ago, I
completely failed to download something from a site after logging in to
it, using the current Firefox on Win8. I then tried the same exercise
with an older Firefox on Linux, and it worked perfectly. Unusual, I
have to say, it's more often the other way around, but clearly the web
developer had done something wrong. The web protocol for downloading is
trivial and shouldn't even require javascript. But something clever had
been done about restricting the download to logged-in account holders,
and it wasn't behaving as expected. Sturgeon's Revelation applies to
websites, and in particular, to their developers.

-- 
Joe

[toc] | [prev] | [next] | [standalone]

#181782

Long Wind <longwind2009@gmail.com> writes:

> this is really unbelievable
> I can't visit this site with jessie/iceweasel

What happens? A server error? A 404 Not Found error? The connection
times out? The browser crashes? A boxing glove on a spring pops out of
the monitor into your face?

> can you help me and test the site?

You'll need to say what actually happens for you, otherwise no-one can
know whether they're experiencing the same.

-- 
 \     “Never do anything against conscience even if the state demands |
  `\                                             it.” —Albert Einstein |
_o__)                                                                  |
Ben Finney

[toc] | [prev] | [next] | [standalone]

#181792

On Tuesday 06 June 2017 01:37:22 Ben Finney wrote:
> Long Wind <longwind2009@gmail.com> writes:
> > this is really unbelievable
> > I can't visit this site with jessie/iceweasel
>
> What happens? A server error? A 404 Not Found error? The connection
> times out? The browser crashes? A boxing glove on a spring pops out of
> the monitor into your face?
>
> > can you help me and test the site?
>
> You'll need to say what actually happens for you, otherwise no-one can
> know whether they're experiencing the same.

I got an error message: "Unknown host www.cs.ecitic.com"

Lisi

[toc] | [prev] | [next] | [standalone]

#181816

> On Tuesday 06 June 2017 01:37:22 Ben Finney wrote:
> > WA boxing glove on a spring pops out of
> > the monitor into your face?
> > 

Sounds like the next step in UI design, in fact, it might be a real "gooey" 
UI.  <sorry>

[toc] | [prev] | [next] | [standalone]

#181831

I visited the site with lynx and got error 521 which I've never 
encountered before. error 500's indicate access is forbidden generally 
if memory serves.

On Tue, 6 Jun 2017, Ben Finney wrote:

> Date: Mon, 5 Jun 2017 20:37:22
> From: Ben Finney <bignose@debian.org>
> To: debian-user@lists.debian.org
> Subject: Re: why can't I visit this web site
> Resent-Date: Tue,  6 Jun 2017 00:37:47 +0000 (UTC)
> Resent-From: debian-user@lists.debian.org
> 
> Long Wind <longwind2009@gmail.com> writes:
>
>> this is really unbelievable
>> I can't visit this site with jessie/iceweasel
>
> What happens? A server error? A 404 Not Found error? The connection
> times out? The browser crashes? A boxing glove on a spring pops out of
> the monitor into your face?
>
>> can you help me and test the site?
>
> You'll need to say what actually happens for you, otherwise no-one can
> know whether they're experiencing the same.
>
>

-- 

[toc] | [prev] | [next] | [standalone]

#181832

On Tue, Jun 06, 2017 at 12:00:47PM -0400, Jude DaShiell wrote:
> I visited the site with lynx and got error 521 which I've never 
> encountered before. error 500's indicate access is forbidden generally 
> if memory serves.

HTTP 521 is "Web server is down", which is really confusing (obviously
it's not down or you wouldn't have been able to connect to it to get
that error).

Googling gives
https://serverfault.com/questions/845544/error-521-cloudflare-with-https-while-http-works
which suggests that perhaps the hostname is pointing to the wrong IP
addreess.

$ host www.cs.ecitic.com
www.cs.ecitic.com is a nickname for www.cs.ecitic.chinacache.net
www.cs.ecitic.chinacache.net is a nickname for f2a4b54c455789a5.cdn.jiashule.com
f2a4b54c455789a5.cdn.jiashule.com has address 219.153.73.220
f2a4b54c455789a5.cdn.jiashule.com has address 219.153.73.219

There are two IPs (basic DNS round robin), so it's possible that
one of them is "right" and one is "wrong", and each person testing
has a 50/50 shot of hitting the "wrong" IP.

[toc] | [prev] | [next] | [standalone]

#181834

Jude DaShiell wrote:
> I visited the site with lynx and got error 521 which I've never 
> encountered before. error 500's indicate access is forbidden generally 
> if memory serves.

500 errors are the server responding that it cannot fulfill your
request.  Wikipedia[1] shows 521 specifically as a custom (i.e. "specific
service only" vs. global) code used by Cloudflare to indicate the target
server is down.

[1] https://en.wikipedia.org/wiki/List_of_HTTP_status_codes


-- 
|_|O|_| Registered Linux user #585947
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5  4AEE 8E11 DDF3 1279 A281

[toc] | [prev] | [next] | [standalone]

#181783

[Multipart message — attachments visible in raw view] — view raw

i am not at home and can't use debian pc

my problem is like Richard's description
it loads sth., but display nothing

thanks!

[toc] | [prev] | [next] | [standalone]

#181786

Long Wind <longwind2009@gmail.com> writes:

> i am not at home and can't use debian pc

That's okay. We can wait until you are able to reply properly.

-- 
 \       “Are you pondering what I'm pondering?” “Umm, I think so, Don |
  `\          Cerebro, but, umm, why would Sophia Loren do a musical?” |
_o__)                                           —_Pinky and The Brain_ |
Ben Finney

[toc] | [prev] | [next] | [standalone]

#181857

On Tue, Jun 06, 2017 at 09:31:26AM +0800, Long Wind wrote:
>    i am not at home and can't use debian pc
>    my problem is like Richard's description
>    it loads sth., but display nothing
>    thanks!

Here is a screen recording of what that abomination of a web page looks 
like.  
https://drive.google.com/file/d/0B84pZZOsDAK5UVNUTXcwZFRUOWs/view?usp=sharing

[toc] | [prev] | [next] | [standalone]

#181815

Just as a data point, it seems to work for me in Wheezy / Iceweasel / Firefox 
ESR--I see lots of content, but all in a foreign language using--what's the 
right word?--pictographs?--those "picture characters" used in several far east 
languages (e.g., Chinese).

On Monday, June 05, 2017 08:12:41 PM Long Wind wrote:
> this is really unbelievable
> I can't visit this site with jessie/iceweasel
> 
> http://www.cs.ecitic.com/
> 
> I can visit it with XP/firefox
> 
> can you help me and test the site?

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | linux.debian.user

csiph-web