is this an AOL thing?

caching problem?

[topr8]

got a little asp application going, it works fine here ...

basically aspupload a pic into a directory then grabbing the path use a form to give the pic a title and description and to enter into a database.

as i said works very sweetly, but have an aol user who can upload one picture and enter the details into the db no prob, but the second one just doesn't work.

is there a caching problem or something with aol?

also any ideas how to show proper error messages with the aol browser? this person says they don't even have a "tools" button.

[jimbeetle]

Hi topr8,

Don't have the exact answer for you but I do think this is an AOL thing, probably its implementation of IE.

We still keep AOL service because we found a lot of inconsistencies a few years back between stand alone IE and AOL's IE (if I remember correctly much of the time with asp pages). There would be times I would have problems with AOL at a site using asp. If I fired up stand alone IE, going through the AOL connection, all would work fine.

Best bet is probably to find a friend with AOL and do some tests. Depending on your audience you can have a heck of a lot of visitors through AOL.

Jim

[topr8]

thanks jim ... well the site works fine, it was just some functions in the admin area.

funily enough they work fine in nn4 so i think it is an aol thing as you suggested, we've just worked around it.

why DO people insist on using aol?

[Iguana]

The main thing about AOL that causes problems is the way it's cache operates. As a user navigates through your site each page request will actually come from a different IP. On a load balanced web farm this causes problems because sessions are sometimes maintained by IP. I don't see why this would affect ASPUpload since each upload should be a discrete transaction