Cedric Lewe
Cedric Lewe
CPU data is comming from LHM not ADLX. Weird that usage works but not temp or power
Waiting for #112
Waiting for #112
Body is encrypted using the randomKey and standard AES in ECB mode with PKCS7 padding. Decryption is done using the same key and parameters. The `x-random-secret-key` is the randomKey encrypted...
The key values for the app are: ```typescript const ACCESS_KEY = "kme8xdq4fp88wps563qd5d57vw6jxrf4" const APP_KEY = "3A51762ED80A39AD3DF3DB3CE6767884" const SECRET_KEY = "MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDlcwFJfpjOsy5U6KBpDEC9ZU_sgjD4AQ_Io0MuuGmQq8wdeLoozOdXRlkyZ2GovikSa6IXMkJ25NeChWGwBDTsnXuvZ3JIFqiTNt5eMtb42u2iHumWtv7fsjj17FFknOIIVzUMPBJ3eIb2" ```
Additionally there is the `x-limit-obj` header that needs to be send on all non-login requests. It is constructed by encrypting the `user_id` with the secretKey using the same RSA method...
I agree, an alternative would be to have a seperate `ctx.RenderString(tpl string)` function but that would be the worse option I think. So going with your suggestion @nilathedragon looks like...
@nilathedragon Do we want this with a separate method, for example ctx.JSONStatus(http.StatusOK, any) or with a magic method that uses 200 OK as the default? Both would not break backwards...
@nilathedragon Also we should probably add the variant we choose for every method not only JSON
> I always really liked the idea of a `ctx.Status(int statusCode) error` function. Instead of immediately writing the status code, the final value would be evaluated and written once the...