mirror of
https://github.com/Finb/bark-server.git
synced 2026-04-26 06:05:52 +03:00
[GH-ISSUE #44] 关于API V2的几点疑问 #35
Labels
No labels
enhancement
in progress
need test
pull-request
v2
v2
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/bark-server#35
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @pppscn on GitHub (Feb 26, 2021).
Original GitHub issue: https://github.com/Finb/bark-server/issues/44
1、/register获取的device_key有效期是多久?
2、/push时一直提示"device key is empty"这是哪里出问题了?
{ "body": "Test Bark Server", "device_key": "lfcepdbexuhyqapx", "title": "bleem", "ext_params": { "url": "https://mritd.com" }, "category": "category", "sound": "minuet.caf" }{ "code": 400, "message": "device key is empty", "timestamp": 1614328454 }3、API_V2.md 中 /push 的java示例 addHeader("Authorization", "Basic Og==") 这个值是哪里来的?
https://github.com/Finb/bark-server/blob/master/docs/API_V2.md
@pppscn commented on GitHub (Feb 26, 2021):
docker 2.0.1 有向前兼容吗?
@pppscn commented on GitHub (Feb 26, 2021):
2021-02-26 08:49:08 INFO 172.20.0.1 -> [400] GET 53.724µs /:device_key/:title/:body => /KL8v4f5fXnEey7KeS6SAqS/%E4%BF%A1%E6%81%AF%E6%9D%A5%E6%BA%90/%E3%80%90%E4%BA%AC%E4%B8%9C%E3%80%91%E9%AA%8C%E8%AF%81%E7%A0%81%E4%B8%BA387481%EF%BC%88%E5%88%87%E5%8B%BF%E5%B0%86%E9%AA%8C%E8%AF%81%E7%A0%81%E5%91%8A%E7%9F%A5%E4%BB%96%E4%BA%BA%EF%BC%89%EF%BC%8C%E8%AF%B7%E5%9C%A8%E9%A1%B5%E9%9D%A2%E4%B8%AD%E8%BE%93%E5%85%A5%E5%AE%8C%E6%88%90%E9%AA%8C%E8%AF%81%EF%BC%8C%E5%A6%82%E6%9C%89%E9%97%AE%E9%A2%98%E8%AF%B7%E7%82%B9%E5%87%BB+ihelp.jd.com+%E8%81%94%E7%B3%BB%E4%BA%AC%E4%B8%9C%E5%AE%A2%E6%9C%8D?isArchive=1&automaticallyCopy=1©=387481
返回400了
@Finb commented on GitHub (Feb 26, 2021):
/register 不用考虑,这是给APP用的一个接口,一般不会手动调用
device_key在APP上可以查看到
你这400,接口返回的错误日志应该有写原因
@pppscn commented on GitHub (Feb 26, 2021):
400的问题已查明,原来1.0.2版本get的时候有addHeader("Content-Type", "application/json; charset=utf-8")导致的,直接删除就好了
@mritd commented on GitHub (Feb 26, 2021):
如果 server 在启动的时候开启了 basic auth(同时设置 user 和 password),服务端会对写请求开启认证,此时 push 请求需要进行标准的 basic auth 授权,如果服务端未开启则默认忽略认证