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.
 

Scope access http won't parse
Author
Previous Topic Next Topic
ST8 ACTOR
Flintlock Asshatery
#1 - 2017-06-06 07:49:45 UTC
Just to be sure that it's not a package issue, I'm meant to pass this for param: 'characterAccountRead%20corporationMembersRead%20esi-mail.send_mail.v1%20esi-skills.read_skills.v1%20esi-skills.read_skillqueue.v1%20esi-wallet.read_character_wallet.v1%20esi-characters.read_corporation_roles.v1'?
Althalus Stenory
Flying Blacksmiths
#2 - 2017-06-06 19:45:22 UTC
put "+" instead of spaces (%20) between scopes, it's more readable and less error friendly :)

Also you should have quotes around these, the param must be 
scope=scope1+scope2+....+scopen

EsiPy - Python 2.7 / 3.3+ Swagger Client based on pyswagger for ESI
Blacksmoke16
Resilience.
#3 - 2017-06-07 02:26:20 UTC
Althalus Stenory wrote:
put "+" instead of spaces (%20) between scopes, it's more readable and less error friendly :)

Also you should have quotes around these, the param must be 
scope=scope1+scope2+....+scopen



It is good to know that the "+" will work, assuming you tested it? The docs say the scope list is a space delimited string, whether that makes a difference i'm not sure.
Althalus Stenory
Flying Blacksmiths
#4 - 2017-06-07 07:38:42 UTC
I use the "+" yes, and often (if i'm not wrong) the + is treated like a space in urls.
So far, i didn't see any differences (and it also saves some characters in the url length) :)

EsiPy - Python 2.7 / 3.3+ Swagger Client based on pyswagger for ESI