On Fri, 19 Jan 2001 20:12:23 +1100, Da Silva, Joe wrote:
> Well, I have now had a chance to try it "your way", after first deleting
----------------snip--------------
> "Your browser sent a request that this server could not understand.
> Request header field is missing colon separator.
> Y=v=1&n=95......."
---------------snip---------------
> So, it appears that different people get different results with this
> Yahoo cookie stuff ... from memory :
> 1. Glenn and Michael had problems with 1.66 but 1.69 was OK.
> 2. You have no problem with either 1.66 or 1.69.
> 3. I have no problem with 1.66 but can't get 1.69 to work.
> So - does this Yahoo cookie problem depend on the PC, the
> PC configuration, the ISP, the country, or perhaps the relative
> humidity, or even the height above sea-level ... ideas anyone ??
Joe,
I just got your post, and went back thru "your way" via www.yahoo.com
with images both off and on, clicking on "Yahoo! Mail" and also on
the "Check EMail" icon. This was after deleting Cookies in my .LST,
and could not get Yahoo to reject any responses from my 1.69...
Everything proceeded smoothly.
-----------few minutes later------------
I just had a thought and did it again, but this time deleted my
COOKIES.LST file instead of just editing it to 0bytes. Same results.
Everything went thru smoothly.
I have found that the FIRST question I really NEED to ask is, "What
am I doing to get the results that I am?" In this case, I can't
see anything different from what you are doing. However, I am a
fiddler...I fiddle with my Arachne Installs relentlessly. You sound
like a fiddler, too. I wonder if there is anything either of us
could have fiddled with in a .CFG file to either make 1.69 work, or
to make it not work...???
Now, I got that "your browser sent a message this server could not
understand" error from the zifdavis eweek servers, all of them (and
still do) with 1.69 but not with 1.66 (which I am now using to read
those eweek pages, until 1.69 gets straightened out). I sent in
a bug report, since several of the other list members confirmed the
affect.
I'm wondering if there IS anything we can do that will mess up the
cooky reply by twiddling and fiddling in our .CFG files, etc.
......gregy
