• Anything ‘published’ on the web is viewed as intellectual property and, regardless of whether it displays a copyright symbol or not, is therefore copyrighted by the originator. The only exception to this is if there is a “free and unrestricted reuse” statement associated with the work.

    In order to protect our members and TFL from possible litigation, all members must abide by the following new rules:

    1. Copying and pasting entire articles from another site to TFL is strictly prohibited. The same applies to articles from print or other media, and to posting photographs taken of copyrighted pages or other media.

    2. Copyright law provides for “fair use” of portions of a copyrighted work. You can copy no more than a SINGLE paragraph from the article to your post (3 or 4 sentences at most).

    3. You must provide a link to the article along with the name of website. For example: ww.xxx.yyy/zzz (The Lower Thumbsuck Daily News).

    4. You must provide, in your own words, a brief summary of the article AND your reasons for believing it will be of interest to TFL members. Failure to do so may result in the thread being closed or your post being deleted as a “cut and paste drive by.”

    5. Photographs and other images are also copyrighted. "Hotlinking" of images (so that it appears in your message) from other sites is also prohibited unless you own rights to the image. If you wish to share an image, provide a clickable link to it.

    Posts that do not follow these new guidelines will be altered or deleted by staff. Members who continue to violate this policy may lose their posting privileges at TFL.

    Thank you for your cooperation and your participation in TFL, the leading online forum for firearms enthusiasts.

Strange Error with Advanced Search and IE8

Against my better judgment, I downloaded IE8 and installed it several days ago. Just today, when I try to use the Advanced Search feature on TFL, I get the "WIndows cannot find connection -> Diagnose Connection" window every time.

When I click on "Diagnose Connection" it immediately loads the screen telling me I can only search every 5 seconds and Windows says "No problem with connection." Every time I hit "Search", the whole process repeats.

Any suggestions?

Another weird one... I went to edit my reply and got the edit window and was actually typing new information in when all of a sudden I got the "This link appears to be broken" window. Obviously, it seems to be working OK now.
 
Last edited:
Just tried in ie8. Works for me. My ie8 security zone setting for the internet at large (including tfl) is medium-high.

Is the computer/browser in question accessing the internet through a wireless connection? If so, perhaps wireless is cutting out?

Does firefox, opera, or chrome have the same problem?

There's always the malware possibility.
malwarebytes
hijackthis

Other than that, all I can suggest is grabbing wireshark and trying to find out if IE8 is sending and receiving the right http data, but a tutorial on wireshark won't fit in the margin here.
 
I have also gotten an intermittent error when searching the forum recently. Using Mac OS 10.5, Safari and Firefox.

I don't recall the exact message, some sort of server error, or non response or something.

I get it exactly if I see it again.
 
Here's the error in Safari:

attachment.php



and Firefox:

attachment.php
 

Attachments

  • Safari.jpg
    Safari.jpg
    116.5 KB · Views: 132
  • Firefox.jpg
    Firefox.jpg
    125.3 KB · Views: 130
Did you get those errors when using the advanced search page, or just the normal search pop-up box? And approximately how often does this happen?

I tried doing a few dozen searches just now (from the search pop-up box, not the advanced search page), and I couldn't reproduce the error (firefox 3.5). There's got to be some other factor.

Also (peetza) it looks like both your firefox and safari versions aren't the latest. I'm sure that has nothing to do with it, just mentioning it because new browser versions often fix security problems...
 
Both at the time, although trying it just now they both work.... intermittent problem apparently. Previously, the pop-up search would give me an error while the advanced search worked....:confused:
 
Are either of you using proxies? Some antiviruses and firewalls do http proxying as well. There seem to be a lot of references on the web to similar problems involving proxies.
 
Additional info:

If I put a "nonsense" search term like "gvajksdfgkhjsda" in the search box, I get and error every time. If I use real words, it's only sometimes.
 
No proxies here, though it is on a wireless connection so it was possible the wireless was cutting out; but at the same time I was having TFL trouble I was still connecting OK to other web sites.

Typically when the wireless cuts out, it is a several minute thing and the Internet doesn't work at all. This would had to have been really brief 30-60 second outages in order to be the wireless. When I get back to the laptop, I'll try Advanced Search again and see if the problem repeats.
 
aha.. peetza gets a cookie, or pizza, or something. Searching for nonexistent words is what reproduced it for me.

BR: Is your IE8 symptom fixed?

There were two lines at the top that I added in when we switched to the sphinx search engine, to show the number of hits for each word in the search string. (I admit it wasn't kosher to output stuff before the html.) Sadly, it appears that vbulletin doesn't enable zlib compression until after those two lines are printed. The http headers tell the browser that the response is compressed, but those two lines weren't, so it threw a fit. They might not have been getting counted in the content-length header, either.

What I don't know is why it was working before. There must have been some behavior change in a recent version of php or lighttpd. It might have been output buffering. Maybe php used to wait until the output buffer was full before it checked whether to compress, and maybe now it compresses on each and every write to the buffer. Seems inefficient, but I have no idea, just guessing.
 
Sadly, it appears that vbulletin doesn't enable zlib compression until after those two lines are printed. The http headers tell the browser that the response is compressed, but those two lines weren't, so it threw a fit. They might not have been getting counted in the content-length header, either.

What I don't know is why it was working before. There must have been some behavior change in a recent version of php or lighttpd. It might have been output buffering. Maybe php used to wait until the output buffer was full before it checked whether to compress, and maybe now it compresses on each and every write to the buffer. Seems inefficient, but I have no idea, just guessing.

Could we get that in English McGee ?
 
Back
Top