10-17-2019, 09:05 PM
I just implemented a new callback and all worked as designed on my dev machine. I'm passing one parameter, in this case '06:00'. Below is the callback output, looks normal:
![[Image: callback-1.png]](https://mjs.us/callback-1.png)
After I moved this app to my server the callback seemed to stop working and this is the output:
![[Image: callback-2.png]](https://mjs.us/callback-2.png)
Thinking it's a parsing issue I base64 encoded the parameter (then decode it to use it).
![[Image: callback-3.png]](https://mjs.us/callback-3.png)
Now everything works. Don't know if this is related to the other callback issues but maybe it's a clue.
After I moved this app to my server the callback seemed to stop working and this is the output:
- The 1st entry looks ok but returns a 302, not 200.
- Following 6 entries immediately come from the app and the parameters are munged starting with the ':' also returning a 302.
Thinking it's a parsing issue I base64 encoded the parameter (then decode it to use it).
Now everything works. Don't know if this is related to the other callback issues but maybe it's a clue.