Naoko 4.3

[Scott Lemmon]

Jor - have you tried messing with the local persistence options at all. I'd be very interested to know if it makes any difference.

Thanks!

 

[JD5000]

OK, I had the same thing happen at yahoo groups right now. (half loaded page) This is what I was getting..

http://home.satx.rr.com/jd5000/images/half.jpg

I went through my config filter by filter.. & I was able to narrow it down to "Insert Style Sheet - Links  {1.d.se}", which inserts my css file into every page.

When I disabled this filter, I was able to load the page 30 times without the half loaded page appearing. Right after this, I enabled it, which caused the half loaded page to appear 7 out of 10 times. Just to make sure, I disabled it again & I was again able to load the page numerous times without error.

I changed the filter to add the styles directly, instead of calling a local file containing the styles. So far, on 20 page refreshes the half loaded problem has not returned.

I dunno if this will help... but.. just incase.

~JD

--------

"Imagination is more important than knowledge" - Einstein

Edited by - JD5000 on 15 Jun 2002  08:34:49

[JD5000]

Forgot..

W98
Opera6
Kerio

--------

"Imagination is more important than knowledge" - Einstein

[Scott Lemmon]

Wish it did help, but when I try inserting a css of my own and I can still load page after page without a hitch.  I've also done quite a bit of testing with a version of the JD5000 config (maybe not the latest - it's at least a few weeks old) but never had a half-loaded page.

Also, didn't someone report it still happening even with the default filter set?  It does seem Kerio may cause some problems, but according to Jor it may not be the culprit here either.

BTW I still haven't heard from anyone about different settings for the local persistent connections and timeouts yet.  I'd *really* like to know if these have any effect on the problem.  





Edited by - Scott Lemmon on 15 Jun 2002  10:01:40

[Arne]

I could mention that I also use Opera from time to time. I have had these half pages with Opera since one of the early 6.02 betas. And I have them still with the Opera 6.03 final. It does not matter if I use Proxomitron or not. Like webattac.com I have not could see the whole page in ages when using Opera. And my problems with half pages when using Opera is not related to Proxomitron at all.

Best wishes
Arne
Imici username= Arne

[Scott Lemmon]

Jor - I just noticed you said you're using pipelining in Mozilla. Turn it off please, it's broken and will cause you all sorts of problems. In testing it seems Mozilla doesn't correctly decode chunked pages when pipelining is enabled. It can loose track of what it's loading, and I'll get stuff like broken images and HTTP headers appearing in the top of iframes.

This would have no effect in Proxomitron 4.2 since without local persistent connections, you can't pipeline. It still wouldn't explain problems in Opera thou. It pipelines by default I believe, and I haven't had any similar troubles when testing it.

Also I understand that you don't normally use the default set and haven't altered the timeouts, but I do need these things tested too.  






Edited by - Scott Lemmon on 15 Jun 2002  10:31:53

[JD5000]

Scott,

When you say "alter timeouts", do you mean the "local connections persist for xx seconds"? If so, I did try setting it to 30 seconds (with no luck) before I started messing with the filters. Does http 1.1 have to be enabled to pipeline? If so, unless they changed it again, Opera by default is set to http 1.0 for proxies.  



--------

"Imagination is more important than knowledge" - Einstein

Edited by - JD5000 on 15 Jun 2002  11:06:02

[cj.]

Scott I just came back to this thread as I have read it days ago.

I too have received a BSOD on my W2K Pro which is a very stable install, and as I had rembered the Kerio usage as the cause I couldn't help but notice that this particular "Stop error" message referred to the "fwdsys.drv": which of course is Kerio.

I was in the midst of a redir and http://www.newsnow.co.uk when it had occured.
I shall keep an eye out again and come back an note any further details. Please note that I have had Kerio ver 2.1.2 running without a hitch since it's install, and yes I am aware of the upgrade now available.

[Jor]

Scott,

spent half an hour browsing with the default.cfg on various sites I know to cause problems, nothing seems to be wrong. That seems to narrow it down to something in my config, right?

Next I tried disabling 'Local connections persist' in Proxomitron's GUI, this didn't help. Got the partial page errors immediately.

Setting them to 30, caused Prox to generate error messages, and die.

Currently browsing with 15 -- no half-loaded pages yet (been browsing 30 mi nutes ).

Also disabled Mozilla's pipeling (but haven't used that browser yet, it is my backup for DHTML sites). Do you know if Mozilla 1.1alpha has better pipelining?

Also, I have HTTP/1.1 enabled for proxies in Opera. Default is disabled.

Edited by - Jor on 15 Jun 2002  18:31:49

[Scott Lemmon]

How do you enable pipelining in Opera then - an ini option? I don't use Opera much myself, but did download it to test with. (BTW I do have "Enable HTTP 1.1 for proxy=1" set)

There might be some difference in a way a filter is working between the two versions of Proxomitron - if you can narrow it down at all that would help.  

Also are you saying seting the connection timeout to 30 caused crashes? That shouldn't be - I normally run it at 60 or higher.






Edited by - Scott Lemmon on 15 Jun 2002  18:22:57

[Jor]

Hmm.. I was too fast. Using '30' doesn't cause a crash anymore.
[Edit] But setting it to 30 or over brings the partially loading pages back [/Edit]

As for Opera's pipelining -- it is enabled by default, when HTTP/1.1 is used (always when not using a proxy, since 6.01 disabled for proxies by default).

To enable pipelining (and other HTTP/1.1 behaviour), Opera6.ini has to be edited, and this string added:

[Proxy]
Enable HTTP 1.1 for proxy=1

(Not yet documented at http://www.opera.com/support/mastering/operaini/ ).

Also, as JD5000 said, the only filter which appears to be involved with this problem, is the 'Insert Prox stylesheet' filter (which in my case includes

<!--//--><link href="http://bweb..local.ptron/prox.css" 
type="text/css" rel="stylesheet" title="Prox CSS" />

$STOP()

on <start>.



Edited by - Jor on 15 Jun 2002  18:32:41

Edited by - Jor on 15 Jun 2002  18:43:04

[Scott Lemmon]

quote:
Also disabled Mozilla's pipeling (but haven't used that browser yet, it is my backup for DHTML sites). Do you know if Mozilla 1.1alpha has better pipelining?

I haven't downloaded it yet, but I've been a bit worried lately - recent versions of Mozilla seems to have *more* networking bugs than before.  Several have been reported but don't seem to be getting fixed.  For example, I notice at Google and Paul's ComputerCops forum Mozilla will often completely load the page twice before rendering it (very annoying because it also happens when posting sometimes).  I first noticed when doing tests with the ALERT command - I had it prompt on each page load.

If you watch Mozilla's progress bar you can see it expand twice too, and it also happens when no proxy is in use. Only at specific sites though - it's as if some bit of HTML on the page triggers it. I was reading some messages about this to the developers who seemed not to believe it was happening, but it's hard to notice unless you have something watching the connections.



 

[Jor]

Going OT of course... but I'm not that happy with Moz 1.0 either. Some of the most useful functions (the link bar for one) have been removed from the code tree, and Javascript menus which work in MSIE, Opera, and Mozilla .097 and earlier do not work anymore. Add to that that Mozilla remains a memory hog, and I don't see it replacing Opera yet...

 

[Scott Lemmon]

Good! That's what I thought about Opera - pipelining is used anytime HTTP/1.1 is.  It's odd that the timeout makes the problem worse.  It works like so: say you have it set to 10 seconds - that means after everything finishes loading, Proxomitron will keep the connection open for up to ten seconds for future requests. That's usually long enough for any images or other stuff related to the page to be requested, but will close everything quickly once the activity drops back to zero.

If you increase the waiting period, that just means the connection is more likely to be reused with future pages, but it depends how long you wait between loading them.  What happens if you turn on "Misc. info" in the log window? It'll show when connections are created and die. Try setting the time-out to 1000 or so to maximize reuse and try loading a bunch of pages. You should see connections being reused - including CSS requests (BTW I figure the browser shouldn't even ask for the CSS on every page - it should be cached).  Also if you have your filters only add your CSS sheet does it still happen (just to rule out other filter interaction)?  Thanks!




 

[Jor]

Hi Scott,

I tested the following:

quote:if you have your filters only add your CSS sheet does it still happen (just to rule out other filter interaction)

It does. I am fairly sure I found what causes the problem: I removed $STOP() from my include Prox CSS filter (see post 2297 in this thread), and no more partially loaded pages. I have no idea why this makes all the difference, but I can load all pages completely now with any value for 'Local connections persist' in Proxomitron, even disabling it!

quote:(BTW I figure the browser shouldn't even ask for the CSS on every page - it should be cached).

Opera6 completely follows the W3C recommendations on HTTP Headers, so reloading the current page (with F5 or the mouse gesture right-click-hold up-down) also requests all images and other linked files on that page. Since Prox serves files with the HTTP Header 'Cache-Control: no-cache', these will always be completely reloaded, effectively bypassing the cache.

Edited by - Jor on 15 Jun 2002  22:08:58