Problem navigating back
|
Aug. 26, 2006, 06:49 PM
Post: #1
|
|||
|
|||
Problem navigating back
Hello,
I noticed that using bfilter often results in inability to navigate back in browser. Here's an example. http://www.storagereview.com/comparison.html click "sort" click one of the drives to see the review now navigate back result: "Warning: Page has Expired " Now make bfilter passive, repeat - the page will show up. This is only one example, in fact I see it quite often. thanks, Vadim Rapp |
|||
Aug. 27, 2006, 06:30 PM
Post: #2
|
|||
|
|||
RE: Problem navigating back
I tried with 3 different browsers, but couldn't reproduce it.
I'll need a traffic capture to solve this. Download WireShark (formerly Ethereal) and start capturing traffic just before you click "Sort". Finish it after "Warning: Page has Expired". Then save it to a file and email it to me. In case you have problems handling WireShark, I can post detailed instructions. |
|||
Aug. 28, 2006, 04:59 PM
Post: #3
|
|||
|
|||
RE: Problem navigating back
> email it to me
what's your email address? |
|||
Aug. 28, 2006, 05:45 PM
Post: #4
|
|||
|
|||
RE: Problem navigating back
jart at users.sourceforge.net
It can be found on the web site. |
|||
Aug. 29, 2006, 07:55 AM
Post: #5
|
|||
|
|||
RE: Problem navigating back
It turned out to be a problem with Internet Explorer. What happens is that IE apparently uses heuristics to decide whether to cache a POST response or not (assuming the response itself doesn't specify it). Because of that, even a small factor can shift its decision. The problem happens when IE decides not to cache the response.
Here are some points: 1. The problem only happens with IE. 2. It only happens if HTTP/1.1 through proxies is enabled. By default it's not. 3. It goes away if you set client_compression=yes in BFilter's Advanced Configuration. 4. It also happens with Proxomitron. So, now you have several options to avoid this problem. I would just drop IE, as other options will affect performance. |
|||
« Next Oldest | Next Newest »
|