Control Private

Control Private

Q&A

Questions
Tags
Users
Feedback

Site feedback
Ask a question

Home
Anonymous
Sign in to post
Post
Explore
Tags
Questions
Site feedback
Articles
Users

Explore

Tags
Questions
Site feedback
Articles
Users

Sign in to post

PatricS
asked
•
May 14 2020 at 11:14 AM
|
ryanchill
commented
•
Jun 05 2020 at 10:54 PM

ryanchill
answered
•
May 15 2020 at 1:40 AM
|
ryanchill
commented
•
Jun 05 2020 at 10:54 PM
Expert Answer Community Expert

Comment ·
Hide
2

PatricS
· May 15 2020 at 8:39 AM

ryanchill
PatricS
· Jun 05 2020 at 10:54 PM

About
·
FAQ
·
Privacy
·
Copyright © 2010-22 DZone, Inc.

When enabling cache in frontdoor, it caches my wordpress sites backend/wp-admin. How and where am i suppose to put cache-control: private ? Do i put it in web.config?
Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.
Correct, you can add your cache control as a rewrite action in your web.config of your wordpress site.
Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.
Thanks, will check it. pattern='. ' , is it here i put the url ' /wp-admin*'
15 people are following this question.

Downloads

Visual Studio

SDKs

Trial software

Free downloads

Office resources

Programs

Subscriptions

Overview

Administrators

Students

Microsoft Imagine

Microsoft Student Partners

ISV

Startups

Events

Community

Magazine

Forums

Blogs

Channel 9

Documentation

APIs and reference

Dev centers

Samples

Retired content

We’re sorry. The content you requested has been removed. You’ll be auto redirected in 1 second.

Marked as answer by
Anonymous
Thursday, October 7, 2021 12:00 AM

Marked as answer by
Anonymous
Thursday, October 7, 2021 12:00 AM

Marked as answer by
Anonymous
Thursday, October 7, 2021 12:00 AM

Marked as answer by
Anonymous
Thursday, October 7, 2021 12:00 AM

Dev centers

Windows

Office

Visual Studio

Microsoft Azure

More...

Learning resources

Microsoft Virtual Academy

Channel 9

MSDN Magazine

Community

Forums

Blogs

Codeplex

Programs

BizSpark (for startups)

Microsoft Imagine (for students)

Newsletter

Privacy & cookies

Terms of use

Trademarks

I don't understand why by default ASP.NET sends a cache-control="private" header to the client? Surely .aspx pages should not be cached because they're dynamic.
But then, it seems that browsers always go back to the server for each request anyway. What's going on?

Cache-Control private says that it's OK for the client to cache the page, subject to its expiration date. The expiration can either be provided with Cache-Control: max-age, or with an Expires HTTP header. In the default case, the page is set
to expire immediately, which means that it won't be cached.
One of the purposes of Cache-Control: private is really to tell intermediate proxies that they should not cache the page.
BTW, just because a page is dynamic doesn't mean that it should never be cached. There are many cases where caching a dynamic page is appropriate. You can cache not only at the client, but also in proxies and in the server's output cache.

(FWIW, I cover this subject in detail in my book).
The book I mentioned is the one in my signature:
Hard to say what's going on. Have you looked at the returned HTML with Fiddler, to see what's happening?
With no Expires or max-age headers, the browser should request the page again if you come to it again. However, browsers are free to do some "extra" caching when you're moving back-and-forth between a requested page in the same browser session.
In general, users (and websites) expect at least a minimal amount of caching on the client. That's why Cache-control: private is the default. If you don't want any caching at all, then you should disable it with NoCache, as you said.

Cache-Control private says that it's OK for the client to cache the page, subject to its expiration date. The expiration can either be provided with Cache-Control: max-age, or with an Expires HTTP header. In the default case, the page is set
to expire immediately, which means that it won't be cached.
One of the purposes of Cache-Control: private is really to tell intermediate proxies that they should not cache the page.
BTW, just because a page is dynamic doesn't mean that it should never be cached. There are many cases where caching a dynamic page is appropriate. You can cache not only at the client, but also in proxies and in the server's output cache.

(FWIW, I cover this subject in detail in my book).
Thanks for your reply. Which is your book (I'm sure you were hoping I'd ask!!)? The main reason I posted is because IE8 is being funny with my pages. I can always reproduce as follows:
No changes appear. Of course, I can see changes by clearing the cache, or pressing Ctrl-F5 - or even just navigating to another page and back. No such problem in Firefox 3.5.

The only cache-related header that is sent is cache-control="private" (no expires, etc). Presumably I can fix with Response.Cache.SetCacheability(HttpCacheability.NoCache) in Global.asax - but I still don't see how this is a good default setting.
Or is this just IE8 being a terrible browser?

The book I mentioned is the one in my signature:
Hard to say what's going on. Have you looked at the returned HTML with Fiddler, to see what's happening?
With no Expires or max-age headers, the browser should request the page again if you come to it again. However, browsers are free to do some "extra" caching when you're moving back-and-forth between a requested page in the same browser session.
In general, users (and websites) expect at least a minimal amount of caching on the client. That's why Cache-control: private is the default. If you don't want any caching at all, then you should disable it with NoCache, as you said.

Table of contents

Exit focus mode

Light

Dark

High contrast

Light

Dark

High contrast

This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Azure Private 5G Core Preview provides flexible traffic handling. You can customize how your packet core instance applies quality of service (QoS) characteristics to traffic. You can also block or limit certain flows.
In 5G networks, the packet core instance is a key component in establishing protocol data unit (PDU) sessions, which are used to transport user plane traffic between a UE and the data network. Within each PDU session, there are one or more service data flows (SDFs) . Each SDF is a single IP flow or a set of aggregated IP flows of UE traffic that is used for a specific service.
Each SDF may require a different set of QoS characteristics, including prioritization and bandwidth limits. For example, an SDF carrying traffic used for industrial automation will need to be handled differently to an SDF used for internet browsing.
To ensure the correct QoS characteristics are applied, each SDF is bound to a QoS flow . Each QoS flow has a unique QoS profile , which identifies the QoS characteristics that should be applied to any SDFs bound to the QoS flow. Multiple SDFs with the same QoS requirements can be bound to the same QoS flow.
A QoS profile has two main components.
A 5G QoS identifier (5QI) . The 5QI value corresponds to a set of QoS characteristics that should be used for the QoS flow. These characteristics include guaranteed and maximum bitrates, priority levels, and limits on latency, jitter, and error rate. The 5QI is given as a scalar number.
You can find more information on 5QI values and each of the QoS characteristics in 3GPP TS 23.501. You can also find definitions for standardized (or non-dynamic) 5QI values.
The required parameters for each 5QI value are pre-configured in the Next Generation Node B (gNB).
Azure Private 5G Core does not support dynamically assigned 5QI, where specific QoS characteristics are signalled to the gNB during QoS flow creation.
Each unique QoS flow is assigned a unique QoS flow ID (QFI) , which is used by network elements to map SDFs to QoS flows.
The packet core instance performs a very similar role in 4G networks to that described in 5G quality of service (QoS) and QoS flows .
In 4G networks, the packet core instance helps to establish packet data network (PDN) connections to transport user plane traffic. PDN connections also contain one or more SDFs.
The SDFs are bound to Evolved Packet System (EPS) bearers . EPS bearers are also assigned a QoS profile, which comprises two components.
A QoS class identifier (QCI) , which is the equivalent of a 5QI in 5G networks.
You can find more information on QCI values in 3GPP 23.203. Each standardized QCI value is mapped to a 5QI value.
An ARP value. This works in the same way as in 5G networks to define an EPS bearer's importance.
Each EPS bearer is assigned an EPS bearer ID (EBI) , which is used by network elements to map SDFs to EPS bearers.
Azure Private 5G Core provides configuration to allow you to determine the QoS flows or EPS bearers the packet core instance will create and bind to SDFs when establishing PDU sessions or PDN connections. You can configure two primary resource types - services and SIM policies .
A service is a representation of a set of QoS characteristics that you want to apply to SDFs that match particular properties, such as their destination, or the protocol used. You can also use services to limit or block particular SDFs based on these properties.
One or more data flow policy rules , which identify the SDFs to which the service should be applied. You can configure each rule with the following to determine when it's applied and the effect it will have:
Optionally, a set of QoS characteristics that should be applied on SDFs matching the service. The packet core instance will use these characteristics to create a QoS flow or EPS bearer to bind to matching SDFs. If you don't configure QoS characteristics, the default characteristics of the parent SIM policy will be used instead.
You can specify the following QoS settings on a service:
SIM policies let you define different sets of policies and interoperability settings that can each be assigned to one or more SIMs. You'll need to assign a SIM policy to a SIM before the UE using that SIM can access the private mobile network.
Top-level settings that are applied to every SIM using the SIM policy. These settings include the UE aggregated maximum bit rate (UE-AMBR) for downloads and uploads, and the RAT/Frequency Priority ID (RFSP ID).
A network scope , which defines how SIMs using this SIM policy will connect to the data network. You can use the network scope to determine the following settings:
You can create multiple SIM policies to offer different QoS policy settings to separate groups of SIMs on the same data network. For example, you may want to create SIM policies with differing sets of services.
Azure Private 5G Core policy control configuration is flexible, allowing you to configure new services and SIM policies whenever you need, based on the changing requirements of your private mobile network.
Tutorial: Create an example set of policy control configuration provides a step-by-step guide th
Naked Wendy
Oh Yes Lingerie
Www Tubent Com En 107743 Double Penetration

Control Private

Report Page