[Bug 39423] New: Voobly: 'Game Browser' can't display content due to Wine built-in browser signature blacklisted on www.voobly.com ('win32' feature token must not be included in user agent string)
wine-bugs at winehq.org
wine-bugs at winehq.org
Sat Oct 10 17:11:09 CDT 2015
https://bugs.winehq.org/show_bug.cgi?id=39423
Bug ID: 39423
Summary: Voobly: 'Game Browser' can't display content due to
Wine built-in browser signature blacklisted on
www.voobly.com ('win32' feature token must not be
included in user agent string)
Product: Wine
Version: 1.7.52
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: urlmon
Assignee: wine-bugs at winehq.org
Reporter: focht at gmx.net
Distribution: ---
Hello folks,
I split this "unrelated" issue out of bug 39408
It's the one that most Voobly users complain about if you search the Internet
and I provide a solution for it.
The 'Game browser' functionality is only available *after* you have logged in.
Without active login/session, clicking the menu item does *nothing* by design.
This shouldn't even work on Windows - I've debugged the QT4 event handler/state
for the menu item.
With active login the game browser window is opened and displays a list of
games at right hand side.
The embedded browser window displays an error page due to Wine's built-in user
agent signature filtered/blacklisted on server side.
--- snip ---
Error 1010 Ray ID: 23320ccc1af12354 • 2015-10-10 11:40:21 UTC
Access denied
What happened?
The owner of this website (www.voobly.com) has banned your access based on your
browser's signature (23320ccc1af12354-fie4).
CloudFlare Ray ID: 23320ccc1af12354 • Your IP: aa.bb.cc.dd • Performance &
security by CloudFlare
--- snip ---
Wireshark:
--- snip ---
POST /client/login HTTP/1.1
Accept: */*
Host: www.voobly.com
Content-Length: 70
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Win32;
Trident/5.0)
Content-Type: application/x-www-form-urlencoded
Accept-Encoding: gzip, deflate
Connection: Keep-Alive
clientsession=foo&uid=bar&url=/homeHTTP/1.1 403 Forbidden
...
--- snip ---
Also mentioned here: http://www.voobly.com/forum/thread/225774
Internet Explorer User Agent Strings:
http://www.useragentstring.com/pages/Internet%20Explorer/
Specifically Internet Explorer 8.0:
--- quote ---
Mozilla/5.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; GTB7.4;
InfoPath.2; SV1; .NET CLR 3.3.69573; WOW64; en-US)
Mozilla/5.0 (compatible; MSIE 8.0; Windows NT 6.0; Trident/4.0; WOW64;
Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729;
.NET CLR 1.0.3705; .NET CLR 1.1.4322)
Mozilla/5.0 (compatible; MSIE 8.0; Windows NT 6.0; Trident/4.0; InfoPath.1;
SV1; .NET CLR 3.8.36217; WOW64; en-US)
Mozilla/5.0 (compatible; MSIE 8.0; Windows NT 6.0; Trident/4.0; .NET CLR
2.7.58687; SLCC2; Media Center PC 5.0; Zune 3.4; Tablet PC 3.6; InfoPath.3)
Mozilla/5.0 (compatible; MSIE 8.0; Windows NT 5.2; Trident/4.0; Media
Center PC 4.0; SLCC1; .NET CLR 3.0.04320)
Mozilla/5.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; SLCC1; .NET
CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET CLR 1.1.4322)
Mozilla/5.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; InfoPath.2;
SLCC1; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET CLR 2.0.50727)
Mozilla/5.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR
1.1.4322; .NET CLR 2.0.50727)
Mozilla/5.0 (compatible; MSIE 8.0; Windows NT 5.1; SLCC1; .NET CLR
1.1.4322)
Mozilla/5.0 (compatible; MSIE 8.0; Windows NT 5.0; Trident/4.0; InfoPath.1;
SV1; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET CLR 3.0.04506.30)
Mozilla/5.0 (compatible; MSIE 7.0; Windows NT 5.0; Trident/4.0; FBSMTWB;
.NET CLR 2.0.34861; .NET CLR 3.0.3746.3218; .NET CLR 3.5.33652; msn
OptimizedIE8;ENUS)
Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.2; Trident/4.0; SLCC2; .NET
CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0)
...
--- quote ---
I wrote a small script which tries all kinds of user-agent combinations and
checks for '403 Forbidden' response
Essentially something like this:
--- snip ---
$ wget --header="Accept: text/html" --user-agent=foo
www.voobly.com/client/login
--- snip ---
Guess what ... it's neither the version nor the platform token - but the
'win32' feature token!
The tokens for 64-bit platforms are accepted or probably not recognized.
The 'win32' token is also absent from the comprehensive list here:
http://www.useragentstring.com/pages/Internet%20Explorer/
My guess would be that users who are now complaining about this, previously
used a 64-bit WINEPREFIX (default) without knowing it (= works) and now
recreated a 32-bit prefix ('WINEARCH=win32').
In future there might be support added to change/fake Wine's built-in user
agent to specific values via registry.
The risk of breakage should be put to the end user -> "you have to deal with
all consequences if you change/do that".
MSDN: https://msdn.microsoft.com/en-us/library/ms537503%28VS.85%29.aspx
("Understanding user-agent strings")
--- quote ---
HKEY_LOCAL_MACHINE (or HKEY_CURRENT_USER)
SOFTWARE
Microsoft
Windows
CurrentVersion
Internet Settings
User Agent
Pre Platform
Token = Value
Post Platform
Token = Value
...
HKEY_LOCAL_MACHINE (or HKEY_CURRENT_USER)
SOFTWARE
Microsoft
Windows
CurrentVersion
Internet Settings
5.0
User Agent
(default) = "Mozilla/4.0"
Compatible = "compatible"
Platform = "Windows NT 5.1"
Version = "MSIE 6.0"
Pre Platform
Token = Value
Post Platform
Token = Value
--- quote ---
$ sha1sum voobly-v2.2.4.38.exe
bf94f42b1a82f797a5578c722ebdf4f5a18b10ab voobly-v2.2.4.38.exe
$ du -sh voobly-v2.2.4.38.exe
11M voobly-v2.2.4.38.exe
$ wine --version
wine-1.7.52-190-gd548639
Regards
--
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.
More information about the wine-bugs
mailing list