Modify SetHeader method in the Context to enable the overriding of existing values.

[claudiamurialdo]

Issue:103629
Starting from #823, headers are set at the beginning of the execution. Therefore, in order for the changes made with the "SetHeader" method to take effect, overriding is necessary.

[genexusbot]

Cherry pick to beta success

• 9511570

[genexusbot]

Cherry pick to beta success

• ac327a0

[ggallotti]

@cmurialdo : This change is ok!

However, I think that the underlying implementation is loosing precision about the Cache-Control Header.

For example, in LigaMX, in order Http Rest Services to be Cacheable by CDN with (stale-while-revalidate) for getting maximum perfornace, I set this:

&HttpResponse.AddHeader(
	!"Cache-Control", 
	Format(!"public, s-maxage=%1, max-age=%1, stale-while-revalidate=15, stale-if-error=%2", 
	&MaxAge.ToString().Trim(), 
	&ErrorSeconds.ToString().Trim())
)

I wonder if this is supported by GeneXus .Net Generator.

This Cache Header is extremly important, as tells the CDN to go only on time to fetch the resource to the origin server, while retuning data from the Cache. It gives max scalability in an app.

Maybe we should use CacheControlHeaderValue.Parse(&CacheControlHeader) instead? Ant then fallback to the original implementation if the Header cannot be parsed.

(Maybe this is should be another Issue)

[genexusbot]

Cherry pick to beta success

• 4a078be

[claudiamurialdo]

@cmurialdo : This change is ok!

However, I think that the underlying implementation is loosing precision about the Cache-Control Header.

For example, in LigaMX, in order Http Rest Services to be Cacheable by CDN with (stale-while-revalidate) for getting maximum perfornace, I set this:

&HttpResponse.AddHeader(
	!"Cache-Control", 
	Format(!"public, s-maxage=%1, max-age=%1, stale-while-revalidate=15, stale-if-error=%2", 
	&MaxAge.ToString().Trim(), 
	&ErrorSeconds.ToString().Trim())
)

I wonder if this is supported by GeneXus .Net Generator.

This Cache Header is extremly important, as tells the CDN to go only on time to fetch the resource to the origin server, while retuning data from the Cache. It gives max scalability in an app.

Maybe we should use CacheControlHeaderValue.Parse(&CacheControlHeader) instead? Ant then fallback to the original implementation if the Header cannot be parsed.

(Maybe this is should be another Issue)

@cmurialdo : This change is ok!

However, I think that the underlying implementation is loosing precision about the Cache-Control Header.

For example, in LigaMX, in order Http Rest Services to be Cacheable by CDN with (stale-while-revalidate) for getting maximum perfornace, I set this:

&HttpResponse.AddHeader(
	!"Cache-Control", 
	Format(!"public, s-maxage=%1, max-age=%1, stale-while-revalidate=15, stale-if-error=%2", 
	&MaxAge.ToString().Trim(), 
	&ErrorSeconds.ToString().Trim())
)

I wonder if this is supported by GeneXus .Net Generator.

This Cache Header is extremly important, as tells the CDN to go only on time to fetch the resource to the origin server, while retuning data from the Cache. It gives max scalability in an app.

Maybe we should use CacheControlHeaderValue.Parse(&CacheControlHeader) instead? Ant then fallback to the original implementation if the Header cannot be parsed.

(Maybe this is should be another Issue)

You are right. That case wasn't working. I changed the code as you suggested.

[genexusbot]

Cherry pick to beta success

• 028b5f3