problems with my first attempt to D/L

[ginahoy]

I'm have Ver 2.0.170, and for the first time, I'm trying to refresh my group (the one Brad downloaded for me last week). Below is my error log. Is there something I'm doing wrong? I left everthing in its default setting.

What's amazing is the amount of time it took for the pgogram to recognize or receive the error (2.5 minutes) and move on to the next message. Also, a large number of bytes were sent back and forth during the process (in excess of 700kB, IIRC).

Also, after receiving the 2nd and 3rd error (but not the first), pgoffline prompted me to "wait" or "stop".  I clicked "wait" after the 2nd error, and "stop" after the 3rd error.  I'm certain I wasn't locked out, because I used IE (via same IP address) while pgoffline was attempting to get the messages, just to make sure the next msg in sequence hadn't been deleted (it hadn't).

David

03/18/04 6:46:32 PM >  Set group's info (eq6)
03/18/04 6:46:32 PM >  Authorization started
03/18/04 6:46:39 PM >  Authorization accomplished
03/18/04 6:46:39 PM >  Request number of messages
03/18/04 6:46:42 PM >  Number of messages : 3781
03/18/04 6:46:42 PM >  Receive message : 3696
03/18/04 6:49:12 PM >  Error : The HTTP redirect request failed

03/18/04 6:49:12 PM >  Receive message : 3697
03/18/04 6:51:48 PM >  Error : The HTTP redirect request failed

03/18/04 6:51:48 PM >  Receive message : 3698
03/18/04 6:53:46 PM >  Time out. Receive stop.
03/18/04 6:54:28 PM >  Error : The HTTP redirect request failed

[ginahoy]

As an update, if I try to refresh the EQ6 group and just let it continue getting the redirect errors, I will get locked out of Yahoo Groups after it attempts about the fourth message or so, even though no messages were retrieved (this takes about 10 minutes). This happened twice last night after my initial post, above.

Using a little utility called DU Meter, I detected over two hundred thousand bytes being transferred back and forth during each message attempt. I didn't think to check how much of that was up and how much was down.

This morning, I added my other three groups and had no problem downloading messages. I only attempted the last few dozen messages (changed starting message from Group Settings). I'll have to wait until another day to D/L the entire groups.

Still no luck with EQ6 group, even though I have no problem browsing the group online.

David

[Wilson Logan]

Hi David,

This error is dealt with in the FAQ:

http://www.pgoffline.com/faq.htm#KK

Effectively, the Yahoo site was busy or unavailable (for maintainance likely).

Cheers,

Wilson.

[ginahoy]

Hi Wilson,
I don't think that's the problem. Recall that I said I was able to use IE to access the group at the same time pgo was getting errors.

Now, I may have figured out what's going on. I noticed that when I set up the EQ6 group in pgo, I used lower case (eq6). But this group is named EQ6, with upper case. Since pgo doesn't have a "rename group" feature, I had to delete the group and reenter with upper case. At that point, I was able to download the messages with no problem. Problem solved!

To verify, I tried to manually enter a link to an individual message in my browser with eq6 in lower case. Guess what...  after 2-1/2 minutes, I got the "cannot find server" error. As soon as I changed to EQ6, I pulled up the message immediately!

So I think it's safe to say that the group name in the message link is case sensitive.

However, I was still puzzled as to why pgo was able to discover the total number of messages when I used the wrong case. I'm not sure what link pgo uses for this, but I was able to load the EQ6 home page by typing in the url using either lower or upper case. Apparently, some pages are case sensitive and others aren't.

Of course, this still doesn't explain why so much bandwidth was used while pgo waited for group to return the error (more than 200kB per message, in 2.5 minutes). Can you check with the developer to see if there's an explanation? This apparently is causing me to get locked out, with only four message attempts in 10 minutes! If there's some sort of unnecessary querry loop going on while waiting for a response (in general), fixing this could go a long way toward extending the number of messages that can be downloaded in a session. Just a thought.

David

[Wilson Logan]

David,

Thanks for the excellent bit of detective work!

Now you've got me thinking.... I'd have thought that using the wrong case either wouldn't matter or you'd simply not gain access.  Its very interesting to see that you could get the number of messages in the group but not the messages themselves.

I'll pass this on to the developer to see what he says about the amount of bandwidth used.

Cheers,

Wilson.