We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I get a problem when use angularQFileUpload on android device in wechat inlay browser。 but it works fine on Web & IOS device。
Here is the mkfile request header:
Request URL:http://up.qiniu.com/mkfile/2267329/key/dGVtcC8xNDQ2MTk5NTQ3NTcx Request Method:POST Status Code:400 Bad Request400 Bad Request Request Headersview source Accept:application/json, text/plain, / Authorization:UpToken LUiQQYHqg151y6uxmda9WpSXt8nYSLqF7nYRKq4G:Est6rIbL1x9Tv7VqzJDmJqZxFXU=:eyJzY29wZSI6InF1YW5xdWFuenUiLCJkZWFkbGluZSI6MTQ0NjIwMzAyMn0= Content-Type:text/plain Origin:http://192.168.1.140:8080 Q-SID:1446199496 Referer:http://192.168.1.140:8080/client/ User-Agent:Mozilla/5.0 (Linux; U; Android 4.4.2; zh-cn; SM-N9005 Build/KOT49H) AppleWebKit/533.1 (KHTML, like Gecko)Version/4.0 MQQBrowser/8.8 TBS/88888888 Mobile Safari/533.1 MicroMessenger/6.2.5.51_rfe7d7c5.621 NetType/WIFI Language/zh_CN Request Payload YFK1MGrfFY2IvYLzNhjBrQGerxw5ue4RFAEjRWeJq83v_ty6mHZUMhDw4dLDAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAMGYIgAAAAAAQUFBQUFBQUFBQUFBQUFBQQ== Response Headersview source access-control-allow-headers:X-File-Name, X-File-Type, X-File-Size access-control-allow-methods:OPTIONS, HEAD, POST access-control-allow-origin:* access-control-max-age:2592000 cache-control:no-store, no-cache, must-revalidate connection:keep-alive content-length:67 content-type:application/json date:Fri, 30 Oct 2015 10:03:58 GMT pragma:no-cache server:nginx/1.4.4 x-content-type-options:nosniff x-log:UP/400 x-reqid:NUUAABsqpQe67hEU
AND the response error here:
{"error":"block 0: expect 2267329 bytes but only 0 bytes uploaded"}
Besides android device get File object doesn't have file.lastModifled but file.lastModifiedDate。 @gitter-badger @chence @icattlecoder
The text was updated successfully, but these errors were encountered:
got the same issue, any update?
Sorry, something went wrong.
同上
No branches or pull requests
I get a problem when use angularQFileUpload on android device in wechat inlay browser。
but it works fine on Web & IOS device。
Here is the mkfile request header:
Request URL:http://up.qiniu.com/mkfile/2267329/key/dGVtcC8xNDQ2MTk5NTQ3NTcx
Request Method:POST
Status Code:400 Bad Request400 Bad Request
Request Headersview source
Accept:application/json, text/plain, /
Authorization:UpToken LUiQQYHqg151y6uxmda9WpSXt8nYSLqF7nYRKq4G:Est6rIbL1x9Tv7VqzJDmJqZxFXU=:eyJzY29wZSI6InF1YW5xdWFuenUiLCJkZWFkbGluZSI6MTQ0NjIwMzAyMn0=
Content-Type:text/plain
Origin:http://192.168.1.140:8080
Q-SID:1446199496
Referer:http://192.168.1.140:8080/client/
User-Agent:Mozilla/5.0 (Linux; U; Android 4.4.2; zh-cn; SM-N9005 Build/KOT49H) AppleWebKit/533.1 (KHTML, like Gecko)Version/4.0 MQQBrowser/8.8 TBS/88888888 Mobile Safari/533.1 MicroMessenger/6.2.5.51_rfe7d7c5.621 NetType/WIFI Language/zh_CN
Request Payload
YFK1MGrfFY2IvYLzNhjBrQGerxw5ue4RFAEjRWeJq83v_ty6mHZUMhDw4dLDAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAMGYIgAAAAAAQUFBQUFBQUFBQUFBQUFBQQ==
Response Headersview source
access-control-allow-headers:X-File-Name, X-File-Type, X-File-Size
access-control-allow-methods:OPTIONS, HEAD, POST
access-control-allow-origin:*
access-control-max-age:2592000
cache-control:no-store, no-cache, must-revalidate
connection:keep-alive
content-length:67
content-type:application/json
date:Fri, 30 Oct 2015 10:03:58 GMT
pragma:no-cache
server:nginx/1.4.4
x-content-type-options:nosniff
x-log:UP/400
x-reqid:NUUAABsqpQe67hEU
AND the response error here:
{"error":"block 0: expect 2267329 bytes but only 0 bytes uploaded"}
Besides android device get File object doesn't have file.lastModifled but file.lastModifiedDate。
@gitter-badger
@chence
@icattlecoder
The text was updated successfully, but these errors were encountered: