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.

Sign up for GitHub

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

Jump to bottom

Partial responses and range requests #2624

Closed
aspnet-hello opened this issue Jan 2, 2018 · 2 comments
Closed

Partial responses and range requests #2624

aspnet-hello opened this issue Jan 2, 2018 · 2 comments
Labels
affected-very-few This issue impacts very few customers area-middleware Includes: URL rewrite, redirect, response cache/compression, session, and other general middlesware enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-response-caching Needs: Design This issue requires design work before implementating. severity-nice-to-have This label is used by an internal tool
Milestone
Backlog

Comments

@aspnet-hello
Copy link

From @JunTaoLuo on Thursday, September 15, 2016 2:09:20 PM

Currently we don't cache partial responses with status code 206. These responses are cacheable but right now the user will need to override our cache policy providers to cache them. Also there is no current mechanism to coalesce overlapping partial responses and no way to serve a portion of the response given range requests.

Copied from original issue: aspnet/ResponseCaching#36
@aspnet-hello aspnet-hello added this to the Backlog milestone Jan 2, 2018
@aspnet-hello
Copy link
Author

From @Tratcher on Thursday, September 15, 2016 2:20:24 PM

One subset of this functionality would be easy to implement, the ability to handle range requests when the full body is available in the cache. Range requests should already work today, we just ignore the range header. If we checked the range header we could send a subset of the body with a 206 status instead.

@aspnet-hello aspnet-hello added Needs: Design This issue requires design work before implementating. feature-response-caching labels Jan 2, 2018
@aspnet-hello aspnet-hello mentioned this issue Jan 2, 2018
Closed
natemcmaster pushed a commit that referenced this issue Nov 15, 2018
@Tratcher
Harden TFM checks #2624
00827e3
@JunTaoLuo JunTaoLuo added affected-very-few This issue impacts very few customers enhancement This issue represents an ask for new feature or an enhancement to an existing one severity-nice-to-have This label is used by an internal tool labels Nov 9, 2020 — with ASP.NET Core Issue Ranking
@JunTaoLuo
Copy link
Contributor

It's unlikely we'll implement this unless there's more demand for this issue.

@ghost ghost locked as resolved and limited conversation to collaborators Dec 16, 2020
@amcasey amcasey added area-middleware Includes: URL rewrite, redirect, response cache/compression, session, and other general middlesware and removed area-runtime labels Jun 2, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
affected-very-few This issue impacts very few customers area-middleware Includes: URL rewrite, redirect, response cache/compression, session, and other general middlesware enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-response-caching Needs: Design This issue requires design work before implementating. severity-nice-to-have This label is used by an internal tool
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
4 participants
@Eilon @JunTaoLuo @amcasey @aspnet-hello