These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

EVE Technology Lab

 
  • Topic is locked indefinitely.
 

IGB and XHR long polling (socket.io)

First post First post
Author
Xinryu
NEXUS Financial
#1 - 2016-07-21 12:50:58 UTC  |  Edited by: Xinryu
So I'm currently testing a microlottery site that I made (https://nexusdev.net/negrand/), and I've noticed that socket.io fails to open a connection to my node app.

Now I wasn't expecting it to support websockets, but I've read posts on the forums stating that it did work with XHR long polling. Since socket.io uses an upgrade process for the connection (XHR -> websockets if available), I'm surprised it doesn't work.

Are there any IGB console-like tools that I could use to troubleshoot this? I'm aware that IGB support is dying soon, but it'd be nice to have this working for the time being

EDIT:
Additional thoughts - is there a specific allowed port range on connections in the IGB?
CCP Tellus
C C P
C C P Alliance
#2 - 2016-07-21 13:04:11 UTC
The IGB is based off of Chrome 3. Try running your application in that browser and see what errors you get.
Carbon Alabel
Gemini Talon
The Curatores Veritatis Auxiliary
#3 - 2016-07-21 13:08:58 UTC
Not really. The IGB is based on Chromium version 3, so you might try finding a version of that.

But spending any amount of time supporting the IGB is an utter waste of it at this point. I'd suggest you use something like this to deter any visitors from using the IGB.

Also, using the SSO on gambling sites is against the Third party developer license agreement: https://developers.eveonline.com/resource/license-agreement
Quote:
The Purpose explicitly excludes (a) any use of the Licensed Materials or CCP Marks for any Application that is not used to support a Player's use of EVE or any related CCP product, and (b) any Application that promotes or provides online gambling, betting, raffles, lotteries, sweepstakes, or similar activities (as determined by CCP, in its sole discretion).
Xinryu
NEXUS Financial
#4 - 2016-07-21 13:30:14 UTC
Carbon Alabel wrote:
Not really. The IGB is based on Chromium version 3, so you might try finding a version of that.

But spending any amount of time supporting the IGB is an utter waste of it at this point. I'd suggest you use something like this to deter any visitors from using the IGB.

Also, using the SSO on gambling sites is against the Third party developer license agreement: https://developers.eveonline.com/resource/license-agreement
Quote:
The Purpose explicitly excludes (a) any use of the Licensed Materials or CCP Marks for any Application that is not used to support a Player's use of EVE or any related CCP product, and (b) any Application that promotes or provides online gambling, betting, raffles, lotteries, sweepstakes, or similar activities (as determined by CCP, in its sole discretion).


Huh, that provision seemed like one that applies to an activity strictly outside of the game world. On that note, with the IGB (and HTTP headers) going away, what will be the proposed/preferred method of authentication/account linking?
Carbon Alabel
Gemini Talon
The Curatores Veritatis Auxiliary
#5 - 2016-07-21 13:38:06 UTC
SSO is both the preferred and most reliable method, but considering you're not allowed to use it (yet) email signup with API key authentication is the best choice.
Xinryu
NEXUS Financial
#6 - 2016-07-21 13:51:37 UTC
Yeah, it feels like using anything other than SSO would be 'swimming against the current', with the way the dev path has been moving.

So in light of all of this, would it be possible for dev to offer some insight here: is there a plan moving forward to permit use of the SSO for any non-nefarious applications? (If there is a specific restriction currently in place; the wording on definitions section 13 reads openly)
Squizz Caphinator
The Wormhole Police
#7 - 2016-07-21 15:57:28 UTC
Xinryu wrote:
Yeah, it feels like using anything other than SSO would be 'swimming against the current', with the way the dev path has been moving.

So in light of all of this, would it be possible for dev to offer some insight here: is there a plan moving forward to permit use of the SSO for any non-nefarious applications? (If there is a specific restriction currently in place; the wording on definitions section 13 reads openly)


This is done on purpose so they can look at your website/application and say "nope". I doubt a dev is going to give you a green light on any type of gambling site involving SSO, even if it's 100% legitimate.

Various projects I enjoy putting my free time into:

https://zkillboard.com | https://evewho.com

Steve Ronuken
Fuzzwork Enterprises
Vote Steve Ronuken for CSM
#8 - 2016-07-21 16:32:49 UTC
Quote:
The Purpose explicitly excludes: [...] B: any Application that promotes or provides online gambling, betting, raffles, lotteries, sweepstakes, or similar activities


That's fairly explicit.

I don't see the clause going away. And I don't see CCP doing anything to make your life easier here.

Woo! CSM XI!

Fuzzwork Enterprises

Twitter: @fuzzysteve on Twitter

Salgare
Center for Advanced Studies
Gallente Federation
#9 - 2016-07-21 17:37:31 UTC
steve, what language/s do you use at Fuzzwork Enterprises?
Xinryu
NEXUS Financial
#10 - 2016-07-22 03:03:55 UTC
Steve Ronuken wrote:
Quote:
The Purpose explicitly excludes: [...] B: any Application that promotes or provides online gambling, betting, raffles, lotteries, sweepstakes, or similar activities


That's fairly explicit.

I don't see the clause going away. And I don't see CCP doing anything to make your life easier here.


As of now, it won't be going live with SSO.

Email/API auth was suggested as a solution for the post-IGB era, but do you know of anything else that may be coming along to provide a way to authenticate characters/users?
Steve Ronuken
Fuzzwork Enterprises
Vote Steve Ronuken for CSM
#11 - 2016-07-22 13:15:16 UTC
Salgare wrote:
steve, what language/s do you use at Fuzzwork Enterprises?



Frontend is php.

Backend stuff runs a mix of php and python. The newer stuff is python.

DB wise, I'm using both mysql and postgres. (mostly mysql, with postgres used where mysql isn't enough. like for window functions)

Woo! CSM XI!

Fuzzwork Enterprises

Twitter: @fuzzysteve on Twitter

Steve Ronuken
Fuzzwork Enterprises
Vote Steve Ronuken for CSM
#12 - 2016-07-22 13:17:17 UTC
Xinryu wrote:
Steve Ronuken wrote:
Quote:
The Purpose explicitly excludes: [...] B: any Application that promotes or provides online gambling, betting, raffles, lotteries, sweepstakes, or similar activities


That's fairly explicit.

I don't see the clause going away. And I don't see CCP doing anything to make your life easier here.


As of now, it won't be going live with SSO.

Email/API auth was suggested as a solution for the post-IGB era, but do you know of anything else that may be coming along to provide a way to authenticate characters/users?



Nothing new.

The old fashioned way of doing it, (because no-one with half a brain used the IGB header) is to have them eve mail you, or send you a little isk, with an identifier in the mail or transaction. Then use the xml API to pull that.

Woo! CSM XI!

Fuzzwork Enterprises

Twitter: @fuzzysteve on Twitter

Xinryu
NEXUS Financial
#13 - 2016-07-22 21:40:46 UTC
Steve Ronuken wrote:
Xinryu wrote:
Steve Ronuken wrote:
Quote:
The Purpose explicitly excludes: [...] B: any Application that promotes or provides online gambling, betting, raffles, lotteries, sweepstakes, or similar activities


That's fairly explicit.

I don't see the clause going away. And I don't see CCP doing anything to make your life easier here.


As of now, it won't be going live with SSO.

Email/API auth was suggested as a solution for the post-IGB era, but do you know of anything else that may be coming along to provide a way to authenticate characters/users?



Nothing new.

The old fashioned way of doing it, (because no-one with half a brain used the IGB header) is to have them eve mail you, or send you a little isk, with an identifier in the mail or transaction. Then use the xml API to pull that.


The 'message on first deposit' idea seemed to be the easiest from an end-user standpoint, so that's the current implementation.

Thanks for the advice, and pointing out the issues regarding use of SSO