You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
Webhook notification with wrong header
I'm using dropbox sdk java 4.0.1. I've configured my webhook url (in the app console) for receiving notification on my server. It works but I receive these headers in the notification:
host my.machine
user-agent DropboxWebhooks/1.0
accept */*
accept-encoding gzip,deflate
X- ropbox-Signature d4exxx65
content-type application/json
content-length 108
(I replaced sensitive data)
As you can see, the header name is wrong. Is it expected? Am I doing something wrong?
There doesn't appear to be anything wrong in these lines, but it's possible the header name is getting corrupted elsewhere in the stack, before the value gets to your code.
- Greg-DB
Dropbox Staff
That header name "X- ropbox-Signature" does look incorrect; it should be "X-Dropbox-Signature". I just tried this myself though, setting up a server to receive Dropbox webhook notifications, and I am receiving the correct "X-Dropbox-Signature" header name, not "X- ropbox-Signature", so there may be something on your webhook URI server corrupting that on the receiving side.
How are you receiving these webhook notifications, and how are you printing out the headers? (The version of the Dropbox Java SDK you're using wouldn't be relevant as that SDK doesn't handle the receipt of webhook notifications; that would be done by your web framework.)
I set the Webhook URI in the App Console. Then my server receives the request and I print it as
Collections.list(request.getHeaderNames()).stream().forEach(h -> log.info(h + " (" + request.getHeader(h) + ")"));
but also reading as
String signature = request.getHeader("X-Dropbox-Signature");is empty.
I'm going to check my code but a part this I should do nothing before...
- Greg-DB
There doesn't appear to be anything wrong in these lines, but it's possible the header name is getting corrupted elsewhere in the stack, before the value gets to your code.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
