What's needed is "-b com.google.Chrome" (without quotes?) to tell OS X to open Chrome as the relay browser.
That worked. Thanks.
Chrome also worked fine as my Relay Browser.
Looking again at psly's log:
Code:
-----From Browser-----
GET /account_combatmacros.php HTTP/1.1
Host: 127.0.0.1:60080
Connection: keep-alive
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.115 Safari/537.36
Accept-Encoding: gzip, deflate, sdch
Accept-Language: en-US,en;q=0.8
Cookie: frcm_style=3; chatpwd=250; [appserver=www11]; appserver=www9; charpwd=266
----------
Requesting: http://www.kingdomofloathing.com/account_combatmacros.php
2 request properties
Field: Cookie = [frcm_style=3; chatpwd=250; [appserver=www11]; appserver=www9; charpwd=266; appserver=www9; PHPSESSID=f2k5lris0phd4ju6bu144jlig5]
Field: User-Agent = [Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.115 Safari/537.36]
Retrieved: http://www.kingdomofloathing.com/account_combatmacros.php
10 header fields
Field: null = [HTTP/1.1 200 OK]
Field: Cache-Control = [no-store, no-cache, must-revalidate, post-check=0, pre-check=0]
Field: Server = [nginx/1.0.15]
Field: Connection = [keep-alive]
Field: Pragma = [no-cache]
Field: Expires = [Thu, 19 Nov 1981 08:52:00 GMT]
Field: Content-Length = [2889]
Field: Date = [Wed, 25 Feb 2015 05:39:45 GMT]
Field: X-Powered-By = [PHP/5.3.3]
Field: Content-Type = [text/html; charset=UTF-8]
-----To Browser-----
HTTP/1.1 200 OK
Server: nginx/1.0.15
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Date: Wed, 25 Feb 2015 05:39:45 GMT
X-Powered-By: PHP/5.3.3
Content-Type: text/html; charset=UTF-8
Content-Length: 3029
Cache-Control: no-cache, must-revalidate
Pragma: no-cache
I see that the browser supplied the following cookies:
Cookie: frcm_style=3; chatpwd=250; [appserver=www11]; appserver=www9; charpwd=266
Those appserver cookies are just wacko - especially since when you connect via the relay browser, we do not propagate those down from KoL. You must have logged in without KoLmafia a few times in the past and Chrome retained, or something.
We sent them up to KoL:
Field: Cookie = [frcm_style=3; chatpwd=250; [appserver=www11]; appserver=www9; charpwd=266; appserver=www9; PHPSESSID=f2k5lris0phd4ju6bu144jlig5]
Notice that we took the browser-supplied list and then appended the ones that we were using to communicate with KoL. It responded and didn't seem to mind. Perhaps I should trim out any "appserver" cookies from the Browser...
Later in the log:
Code:
-----From Browser-----
GET /newchatmessages.php?aa=0.590283774305135&j=1&lasttime=1397264456 HTTP/1.1
Host: 127.0.0.1:60080
Connection: keep-alive
Accept: application/json, text/javascript, */*; q=0.01
X-Requested-With: XMLHttpRequest
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.115 Safari/537.36
Referer: http://127.0.0.1:60080/mchat.php
Accept-Encoding: gzip, deflate, sdch
Accept-Language: en-US,en;q=0.8
Cookie: frcm_style=3; chatpwd=250; [appserver=www11]; appserver=www9; charpwd=266
----------
class net.sourceforge.kolmafia.request.ChatRequest
Connecting to newchatmessages.php...
Requesting: http://www.kingdomofloathing.com/newchatmessages.php?j=1&lasttime=1397264456
2 request properties
Field: Cookie = [appserver=www9; PHPSESSID=f2k5lris0phd4ju6bu144jlig5]
Field: User-Agent = [Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.115 Safari/537.36]
Retrieving server reply...
Retrieved: http://www.kingdomofloathing.com/newchatmessages.php?j=1&lasttime=1397264456
10 header fields
Field: null = [HTTP/1.1 200 OK]
Field: Cache-Control = [no-store, no-cache, must-revalidate, post-check=0, pre-check=0]
Field: Server = [nginx/1.0.15]
Field: Connection = [keep-alive]
Field: Pragma = [no-cache]
Field: Expires = [Thu, 19 Nov 1981 08:52:00 GMT]
Field: Content-Length = [44]
Field: Date = [Wed, 25 Feb 2015 05:39:48 GMT]
Field: X-Powered-By = [PHP/5.3.3]
Field: Content-Type = [text/html; charset=UTF-8]
Retrieving server reply
ResponseText has 44 characters.
{"msgs":[],"last":"1397264459","delay":3000}
-----To Browser-----
HTTP/1.1 200 OK
Date: Wed Feb 25 00:39:48 EST 2015
Server: KoLmafia v16.8
Content-Type: text/html; charset=UTF-8
Cache-Control: no-cache, must-revalidate
Pragma: no-cache
Connection: close
{"msgs":[],"last":"1397264459","delay":3000}
----------
Even though the Browser requested newchatmessages.php, we internally converted that into a ChatRequest and, therefore, did not include the browser-supplied cookies.
This was immediately followed by:
Code:
Loading window: LoginFrame
Logout in progress (interface will be unresponsive)...
Preparing for logout...
Sharing mall price data with other users...
You have no updated price data to submit.
Requests complete.
Sending logout request...
class net.sourceforge.kolmafia.request.LogoutRequest
Connecting to logout.php...
Requesting: http://www.kingdomofloathing.com/logout.php
1 request properties
Field: User-Agent = [Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.115 Safari/537.36]
Retrieving server reply...
Retrieved: http://www.kingdomofloathing.com/logout.php
8 header fields
Field: null = [HTTP/1.1 302 Found]
Field: Server = [nginx/1.0.15]
Field: Connection = [keep-alive]
Field: Content-Length = [0]
Field: Date = [Wed, 25 Feb 2015 05:39:49 GMT]
Field: Location = [loggedout.php]
Field: X-Powered-By = [PHP/5.3.3]
Field: Content-Type = [text/html; charset=UTF-8]
KoLmafia logged you out. I did a grep for "Logout in progress" and found it in KoLmafia.quit.
Code:
./chat/ChatManager.java:584: KoLmafia.quit();
./request/LoginRequest.java:348: KoLmafia.quit();
./swingui/LoginFrame.java:163: KoLmafia.quit();
./swingui/SystemTrayFrame.java:262: KoLmafia.quit();
./textui/command/ExitCommand.java:49: KoLmafia.quit();
./webui/RelayServer.java:162: KoLmafia.quit();
1) If you are a buffbot, any one in your clan can tell you to log off, using chat
2) If you are already logging in and we want to timein, we can't handle it
3) We can log you out from the login frame, somehow
4) You can exit via the System Tray
5) You can use the "exit" command
6) We can try to open a server socket, using port 60080 up to 60089, and not succeed in doing so.
None of those really make any sense.