Noticed a bug - Page 2 - ZR-1 Net Registry Forums

DaveK · 08-05-2012

From what you have described I think you must be right Scott. Some kind of mouseover link (or possibly a timed redirect). If it can be isolated it may be that we can remove it. If this is a document created by Kurt and just loaned to the registry though we may not have the 'right' to edit it though.

I'm not saying we can't - just that we're not at the moment sure of the exact origins or 'license' that the reigistry has to make it available on the site.

Taking it down is easy enough, but then we're taking away a resource that obviously people are downloading/using.

If you can take a look and try isolate it Scott that would be great.

Thanks

Dave

scottfab · 08-06-2012

Ok here is what I've found so far and a work around of sorts.

1. The error while most objectionable on 4a is easier to manifest and reproduce using just 4.

That's because the GET call to www.whiteacingpruducts.com is to a sub element that is missing so you get a "404 file not found" instead of a whole series of page and elements loading.

2. The workaround is as Dave suggested. Save the PDF page and do not open it via your browser but use the adobe reader directly. From within the reader, setup a block on any call to the whiteracing site. I can get more detail and steps to do this on here if someone needs it.
What this does is allow you to scroll the doc without being ejected out to that page. You do get a dialog each time it runs into the "GET" call that the site is blocked but you just hit OK and continue scrolling. At least then you can get to the text on that page.

David, I'd suggest some sort of warning to the user at the point where the link is made to the PDF file of this bug. (and work around)

Other workarounds maybe better like having users putting a block to the site on their firewall but given most will not know too much about this I'd suggest staying with the block from the adobe reader.

I have screen shots and logs using the Firefox webdeveloper web console for all this but it's easy enough for any one to run and capture.
The root cause fix would be for the PDF file to be edited by the owner to remove the calls.

That's it. Time to go out in the scalding weather and sweat.

08-05-2012	#11
DaveK Join Date: Jul 2004 Location: Sudbury, Ontario. Canada Posts: 1,538	Re: Noticed a bug From what you have described I think you must be right Scott. Some kind of mouseover link (or possibly a timed redirect). If it can be isolated it may be that we can remove it. If this is a document created by Kurt and just loaned to the registry though we may not have the 'right' to edit it though. I'm not saying we can't - just that we're not at the moment sure of the exact origins or 'license' that the reigistry has to make it available on the site. Taking it down is easy enough, but then we're taking away a resource that obviously people are downloading/using. If you can take a look and try isolate it Scott that would be great. Thanks Dave __________________ 1991 #1516 Black/Black davidmkelly.com "Speed is often confused with insight." - Johan Cruijff

08-06-2012	#12
scottfab Join Date: Jan 2009 Location: Portland Oregon metro area (Washington side) Posts: 3,207	Re: Noticed a bug Ok here is what I've found so far and a work around of sorts. 1. The error while most objectionable on 4a is easier to manifest and reproduce using just 4. That's because the GET call to www.whiteacingpruducts.com is to a sub element that is missing so you get a "404 file not found" instead of a whole series of page and elements loading. 2. The workaround is as Dave suggested. Save the PDF page and do not open it via your browser but use the adobe reader directly. From within the reader, setup a block on any call to the whiteracing site. I can get more detail and steps to do this on here if someone needs it. What this does is allow you to scroll the doc without being ejected out to that page. You do get a dialog each time it runs into the "GET" call that the site is blocked but you just hit OK and continue scrolling. At least then you can get to the text on that page. David, I'd suggest some sort of warning to the user at the point where the link is made to the PDF file of this bug. (and work around) Other workarounds maybe better like having users putting a block to the site on their firewall but given most will not know too much about this I'd suggest staying with the block from the adobe reader. I have screen shots and logs using the Firefox webdeveloper web console for all this but it's easy enough for any one to run and capture. The root cause fix would be for the PDF file to be edited by the owner to remove the calls. That's it. Time to go out in the scalding weather and sweat. __________________ Scott Vett owner since 1979._It's about the car and the people