The current ShareX implementation does not cover the wide range of different authentication implementations that many different hosts use.
As examples:
upload.systems - Uses the multipart key body property for authentication.
Ascella - Uses the Authorization request header for authentication.
Tixte - Uses the Authorization request header for authentication.
e-z - Uses a key request header for authentication.
The current system only supports custom body props, by defining them in the ShareX JSON config file.
The proposed syntax for the new JSON config file is as follows:
As of 5d85b9493bf409844cfe73f7a7b051ed255c3534, it is now possible to add props for both headers and the body, meaning that most (if not all) ShareX hosts should now be supported.
The current ShareX implementation does not cover the wide range of different authentication implementations that many different hosts use.
As examples: upload.systems - Uses the multipart
key
body property for authentication. Ascella - Uses theAuthorization
request header for authentication. Tixte - Uses theAuthorization
request header for authentication. e-z - Uses akey
request header for authentication.The current system only supports custom body props, by defining them in the ShareX JSON config file.
The proposed syntax for the new JSON config file is as follows: