[Bug 31159] League of Legends: store doesn't load with builtin wininet

[wine-bugs at winehq.org]

http://bugs.winehq.org/show_bug.cgi?id=31159

Tom <tewinget at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tewinget at gmail.com

--- Comment #10 from Tom <tewinget at gmail.com> 2012-07-14 00:23:23 CDT ---
(In reply to comment #9)
> To clarify a little more on how lol store behaves:
> With builtin wininet:
> Store page does't work at all, it is always black. In user profile where there
> are shortcuts to buy champions, the buy button is gray and tooltip says: "Store
> is currently unavailable."
> With native wininet:
> User profile shortcuts always work (this is how I'm currently buying
> champions).
> Store page (this is where my logs come from) loads very slowly and in parts.
> Looks like it's is waiting for some sort of timeout as it loads part of the
> store first than waits and loads another part then waits..... Sometimes it
> loads immediately. But it does eventually start to work.
> 
> Should I post logs from loading user profile (shortcuts to store)? I think it
> still needs to connect to the store, but without loading the page.
> 
> I will do wireshark traces when I come to my home computer (probably not
> today).

I can verify that for me it throws Unknown CA in wireshark and when I look at
the Certificate part of the handshake it shows that only the
lq.na1.lol.riotgames.com cert is passed for the store connection.  For the
login connection, the whole chain is sent, I suppose the store assumes that
windows caches the chains (could this have something to do with wininet
complaining that it doesn't handle persistent cookies?) but it seems maybe wine
doesn't?

I can attach a pcap if someone needs, but I think I described the important
bits well enough here.  Also, if you hack the source to say "sure, that cert is
fine, why not?" it still doesn't work.  The server throws Encrypted Alert
later, implying that the client encrypted something wrong (or rather, that the
client failed to extract something it needed from the cert?).

Sorry to just barge in here with my observations, but I've been dissecting wine
source code every day after work this week, Sunday.  It's wearing me down :(

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.