Skip to content

Add Content-Length header to HTTP response in FilesRouter #2408

New issue

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

Merged

Conversation

vbsteven
Copy link
Contributor

Files served by the old Parse.com service always have a Content-Length header attached. This patch adds the same header to files served by the parse-server.

@TylerBrock
Copy link
Contributor

Thanks for contributing and making the project a great one!

@TylerBrock TylerBrock merged commit 8d8192b into parse-community:master Aug 4, 2016
@gowridev
Copy link

@TylerBrock @flovilmart, trying to read the downloaded file chunk size (while downloading a file from parse file URL), we are getting -1 when trying to access "totalBytesExpectedToWrite" function (in objective C) . I think, there some issue with Content-Length header may be not getting updated (referring to FilesRouter.js).
Could please guide us in this regard.

ios code is given below

(void)URLSession:(NSURLSession )session downloadTask:(NSURLSessionDownloadTask )downloadTask didWriteData:(int64_t)bytesWritten totalBytesWritten:(int64_t)totalBytesWritten totalBytesExpectedToWrite:(int64_t)totalBytesExpectedToWrite

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants