Conversation
User can use a JSON map defined to insert additional headers. Hack is backwards compatible as it looks for a colon : that should not be used in base64 encoding required for the 'authorization' header. Example:
"x-api-key" : "{apikey}", "authorization" : "{apikey}", "Public-Key-Pins": "max-age=2592000; pin-sha256=\\"E9CZ9INDbd+2eRQozYqqbQ2yXLVKB9+xcprMF+44U1g=\\";"
Updated to allow a true JSON string and check for "{ }" instead of ":"
Merge pull request
|
Thanks! I noticed that |
|
Will look at it. Shouldn't be a problem to do that later today. |
|
All yours. State and Atomic are strange birds in ST land. |
Merge with master
|
Is this finished? I wasn't able to trace where |
|
Yes, it is complete. It is a little tricky they way it is called and took some time to figure out, but it is filled here: It doesn't load on the web interface and shows "null" from the .toString() method. This is expected behavior. |
See discussion here: https://community.webcore.co/t/piston-external-url-value-available-to-self/13983