| | Re: jump.cgi David Schilling
|
| | (...) Can't help you there, I only have MSIE. (...) I did a screen capture of #2; you'll find it located temporarily at (URL) if you want. -- David Schilling (24 years ago, 14-Aug-00, to lugnet.admin.general)
|
| | |
| | | | Re: jump.cgi Todd Lehman
|
| | | | (...) OK, good, then this has nothing to do with jump.cgi per se (not that I thought it did, but it's better to be sure just in case). You're seeing the same thing from a different redirector. (The display.cgi script simply picks apart the ng name (...) (24 years ago, 14-Aug-00, to lugnet.admin.general)
|
| | | | |
| | | | | | Re: jump.cgi David Schilling
|
| | | | (...) the first time it was this fast. Multiple times didn't improve the speed at all. (...) the delay. I didn't get a delay with mimg.cgi, (the first link) though. By the way, how did you get those long urls to not split across lines? -- David (...) (24 years ago, 15-Aug-00, to lugnet.admin.general)
|
| | | | |
| | | | | | Re: jump.cgi Todd Lehman
|
| | | | (...) OK, that makes sense. It's only accessing one server there once the image is cached, and then it gives you a large image file. (...) That's totally bizarre too. Another redirection script on a completely different site, presumably doing (...) (24 years ago, 15-Aug-00, to lugnet.admin.general)
|
| | | | |