I have blocked google-analytics.com via the proxy server block list. If I
point the browser at http://ssl.google-analytics.com/ I get an error as
follows:
Cache Error!
The following error has occured: The request you made has been filted
Generated by tinyproxy (1.6.3)
Ok, so it looks like the filter is working. I now point the browser at
https://ssl.google-analytics.com/ and this gives a different error:
Proxy Server Refused Connection
The connection was refused when attempting to contact the proxy server you
have configured. Please check your proxy settings and try again.
Currently I am getting a wait for infinity on some websites. On examination
of the websites concerned, these appear to contain a line of javascript
as follows:
<script src="https://ssl.google-analytics.com/urchin.js";
type="text/javascript">
Obviously google-analytics is never going to respond, because the source is
blocked by proxy.
My question is, what should happen here?
Should the browser timeout here, and continue to download the rest of the
web page?
Would the browser timeout, if the proxy returned a different message
(such as the Cache Error)
Is the browser failing to time out, because the proxy is returning
Proxy Server Refused Connection, so the browser keeps trying?
What is at fault here?
My initial guess is that the proxy is at fault for returning the wrong error
code (I don't think that the proxy should be refusing connection here, but
should instead be returning Cache Error! The following error has occured:
The request you made has been filted.)
I also think that there is a fault in the browser, in that if the proxy
refuses connection, the browser should generate an error, and continue loading
the rest of the page.
I need the facility to skip waiting for infinity, and continue to load the
rest of the page.
Mark.
--
Mark Hobley
Linux User: #370818 http://markhobley.yi.org/
> I have blocked google-analytics.com via the proxy server block list. If I
> point the browser athttp://ssl.google-analytics.com/I get an error as
> follows:
> <script src="https://ssl.google-analytics.com/urchin.js";
> type="text/javascript">
> Obviously google-analytics is never going to respond, because the source is
> blocked by proxy.
> My question is, what should happen here?
The page cannot possibly be rendered.
> I also think that there is a fault in the browser, in that if the proxy
> refuses connection, the browser should generate an error, and continue loading
> the rest of the page.
>
> I need the facility to skip waiting for infinity, and continue to load the
> rest of the page.
Why load a page it cannot render?
You are at fault for denying access to a resource required to render
the page.
DS
Can't it render with the included information missing? Like for example, it
does if an image fails to load?
What do you reckon the browser should do in this case?
> Why load a page it cannot render?
I don't need the advertisements from the blocked sites, but I would like to
see the remaining content.
> In comp.infosystems.www.authoring.toolsDavid Schwartz <dav...@webmaster.com> wrote:
> > The page cannot possibly be rendered.
> Can't it render with the included information missing? Like for example, it
> does if an image fails to load?
No.
> What do you reckon the browser should do in this case?
> > Why load a page it cannot render?
> I don't need the advertisements from the blocked sites, but I would like to
> see the remaining content.
Unfortunately, all the page author need to is design the page so that
it cannot be rendered without the advertisements and there is nothing
you can do. Not all pages are designed this way, but this one is. The
browser has no idea whether or not the script is critical.
DS
Well, it is possible to disable Javascript altogether, and the page loads just
fine then.
Supposing a Javascript cannot be found (eg an HTTP404 error), should the
browser wait for infinity then too, or should it skip trying?
> Well, it is possible to disable Javascript altogether, and the page loads just
> fine then.
Right, but that's a human's decision which the browser has to honor.
> Supposing a Javascript cannot be found (eg an HTTP404 error), should the
> browser wait for infinity then too, or should it skip trying?
It should probably refuse to render the page. That's a pretty tough
call -- is it better to provide nothing at all or to possible provide
something completely inappropriate?
DS
I suppress google analytics via /etc/hosts and have a (very) dumb
webserver that responds to a get with "Sorry, this is all you're
getting here :-)".
When I go to that page, that's all I see, both with js on or off.
Jerry
The author should include in each script the creation of a variable
specific to that script. A page calling for that script can test for
the existence of that variable and branch accordingly; it can use an
alternative script or page, emit an abusive or apologetic remark, etc.
It's a good idea to read the newsgroup c.l.j and its FAQ. See below.
--
(c) John Stockton, nr London UK. ?@merlyn.demon.co.uk IE8 FF3 Op10 Sf4 Cr4
news:comp.lang.javascript FAQ <URL:http://www.jibbering.com/faq/index.html>.
<URL:http://www.merlyn.demon.co.uk/js-index.htm> jscr maths, dates, sources.
<URL:http://www.merlyn.demon.co.uk/> TP/BP/Delphi/jscr/&c, FAQ items, links.