Skip to content
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

cf curl don't pass custom headers to new request for 302 respose #318

Closed
tsl0922 opened this issue Jan 4, 2015 · 2 comments
Closed

cf curl don't pass custom headers to new request for 302 respose #318

tsl0922 opened this issue Jan 4, 2015 · 2 comments

Comments

@tsl0922
Copy link

tsl0922 commented Jan 4, 2015

I'm using the http Range headers on cf curl to get partial of a file, but it doesn't work.

CF_TRACE output:

cf curl /v2/apps/e0a39c2b-aab7-4a19-8463-7ec0dbbfba14/instances/0/files/logs/staging_task.log -H 'Range: bytes=10-1024' -v

REQUEST: [2015-01-04T11:11:38+08:00]
GET /v2/apps/e0a39c2b-aab7-4a19-8463-7ec0dbbfba14/instances/0/files/logs/staging_task.log HTTP/1.1
Host: api.coding.io
Accept: application/json
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/json
Range: bytes=10-1024
User-Agent: go-cli 6.8.0-b15c536 / darwin

REQUEST: [2015-01-04T11:11:38+08:00]
GET /instance_paths/4a02cda394e942fabc6a6a1169d66f07?hmac=696448e2c35e2f3076a9305d725ede77611c907f6fb2104c6be64ed6688a325bf9cc4e67f05de91cfead258159070715390828eb6ebe72d09639e8a3bc60c9e3&path=logs%2Fstaging_task.log&timestamp=1420341098 HTTP/0.0
Host: 75414404eac549d9b713608b8987038a.coding.io
Authorization: [PRIVATE DATA HIDDEN]

RESPONSE: [2015-01-04T11:11:38+08:00]
HTTP/1.1 200 OK
Content-Length: 2320
Accept-Ranges: bytes
Content-Type: text/plain; charset=utf-8
Date: Sun, 04 Jan 2015 03:11:38 GMT
Last-Modified: Sat, 03 Jan 2015 15:41:22 GMT
@cf-gitbot
Copy link

We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/85381498.

@jberkhahn
Copy link
Contributor

This issue has been fixed with the merging of #321.

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

No branches or pull requests

3 participants