GwG Auction House Login

Yes was talked about earlier, however the topic differed, found here::
http://www.guildwarsguru.com/forum/s...ad.php?t=96228

I am wondering if it also a server side problem if i am on the auction site, and every time i link to certain pages i get logged out. EVERY time i click on Auction "home" it logs me back out. I have "Remember Me" checked every time i log back in. So could this also be client side issues?

if this is truely redundant, then delete me. Otherwise, please address this...
thx!

EDIT:: I just tried FFF_WarRaven advice from that other post, and it didnt change a thing... it seems to be a server side thing. Can this be changed? In other words, it would be great to have it recognize my login whenever i go there, like forums do. Don't wanna retype EVERY time i go there and EVERY time i reset to the auction home page...i mean...cmoooon

To improve server performance, we are currently caching the homepage of the auction. This will always say you are logged out, you aren't. We are working on a better solution for this right now but the stability and quickness of the auctions was a first priority (I'm sure you would agree). If you Log In with your Username and Password and click Remember Me, you are logged in. Disregard what the homepage tells you

Hey Inde. I expirienced the same problem, but when it says you are logged out you are actually logged out, it asks you to login back or register. This only happens if you visit home page, then you get logged out, no matter you put remember or not. Tested out in IE; Mozilla & Opera, same result in each.

We're almost done coding it... it'll be fixed in the next day or 2!

btw, I don't know how is your server setted up & how is your auction script written, but usually I use for my & clients websites a zlib.output_compression in .htacccess to speed up the load of text. Maybe you should try it if that already isn't implemented. I think it even works better than gzip, tough, both aren't compatible, error shows up i that case.

Cheers!

A server loaded in this situation is more burdened by CPU process than by bandwidth constraints - so while compressing the page may send the data to you faster, the added load (when the server is already overloaded) makes the net effect neutral, or even negative.

Lets not also forget that in a compressed scheme, the entire HTML must be downloaded before the browser can render it. In a non compressed, it can start rendering it the moment it receives it

Quote: Originally Posted by Inde