Has Evernote changed the HTTP request header validation in the latest update? Our API call for getting access token has failed after the update. It seems the reason of the error is no Content-Length header in the request.
相关问题
- Simple C# Evernote API OAuth example or guide?
- Android: Evernote style layout
- How did Evernote implement their rich text editor
- How to transition from UICollectionView to UIViewC
- Faking standard input on the Windows command line
相关文章
- How to transition from UICollectionView to UIViewC
- Faking standard input on the Windows command line
- Can't load Python modules installed via pip fr
- 哈哈!我就这样被印象笔记拉黑了
- 为什么我会得到试图与Evernote的认证时,KeyError异常?(Why am I gettin
- 新品BOOX Note2发布!全球首款10.3英寸安卓9.0系统电纸书
- 3款被吹爆的iPad应用软件
- Evernote does not update note if a tag is deleted
This should be a side-effect of the Evernote's move to the cloud. Google's load balancers do some HTTP request validation that Evernote was not previously doing: https://cloud.google.com/compute/docs/load-balancing/http/
So for your case, adding the content-length header should fix the issue.