Skip to content

Releases

pipeline/4.5.130

Choose a tag to compare

@Automation51D Automation51D released this 13 Nov 01:57
8b3220b

This release moves .NET toward one behavior across every 51Degrees language. Each element it changes now follows the published 51Degrees specifications, which in turn follow the RFCs they cite, so that the same input gives the same answer in .NET, Java, Node.js, Python, PHP, Go, Rust and C. .NET was the reference the other languages were aligned to, so many of its changes are small. The native libraries take the C library release 51degrees-cxx 4.5.105. Each change names the package family it is in.

This release adds .NET 10. Every package gains a net10.0 build and keeps the builds it had, so a .NET 10 application now loads code built for .NET 10, where it loaded the .NET 8 or .NET Standard 2.0 build before. One kind of .NET 10 web application has to raise two package versions before it will restore, which is set out under "Before you upgrade".

Before you upgrade

  1. The client-side ETag is a weak entity tag. The JavaScript and JSON endpoints send W/"...", where they sent a bare number, and compare If-None-Match weakly, as RFC 9110 section 8.8.3 and section 13.1.2 ask. Code that reads the ETag as a number needs to allow for W/ and the double quotes (#96, pipeline).
  2. Web integration options in a configuration file now take effect. On ASP.NET Core nothing bound PipelineWebIntegrationOptions to the configuration, so the defaults always applied. A file that sets ClientSideEvidenceEnabled or UseSetHeaderProperties to false now turns that feature off, so check both values (#115, pipeline).
  3. Usage Sharing accepts no Evidence. It reads the web request instead, so a Pipeline that holds it no longer accepts every header. A Flow Element of your own that read a header it did not declare must name the key in its EvidenceKeyFilter, or read the request from the new server.http-request Evidence value (#100, pipeline).
  4. An application that builds its own Evidence has to give Usage Sharing the web request. This applies to an application that adds a value to Evidence only when EvidenceKeyFilter on the Pipeline or the Flow Data includes its key. An application that uses the web integration has nothing to change. Up to pipeline 4.5.129 Usage Sharing accepted the headers it shares, so that check kept them. Usage Sharing now accepts none, so the same check drops every header that no other Flow Element reads, and those headers stop being shared. Add the request to the Flow Data under Constants.EVIDENCE_HTTPREQUEST_KEY in FiftyOne.Pipeline.Core, which is server.http-request. The value is an IReadOnlyDictionary<string, object> that holds each value of the request under the key it would have as Evidence, such as header.user-agent, cookie.51D_ScreenPixelsWidth, query.name and server.client-ip. Usage Sharing shares every Evidence value in the Flow Data, then each value of that dictionary whose key the Evidence does not hold. Its rules still apply, so the Cookie header, a blocked header and a cookie whose name does not start 51D_ are left out. The dictionary itself is never shared, is not sent to the cloud service and takes no part in a cache key. On ASP.NET Core, IWebRequestEvidenceService.AddEvidenceFromRequest in FiftyOne.Pipeline.Web adds the request for you (#100, pipeline).
  5. On .NET Framework, session Evidence is renamed. A session value is session.<name> and the session object is session.session, where they were <name> and session (#100, pipeline).
  6. IpiOnPremiseEngineBuilder defaults to the Balanced performance profile. With no profile set it loaded the whole Data File into memory. Call SetPerformanceProfile(PerformanceProfiles.MaxPerformance) to keep the old behavior. IpiOnPremisePipelineBuilder already used Balanced (#102, ip-intelligence).
  7. A client IP value is read only when all of it is one address. .NET read the first entry of a list, trimmed white space and dropped a zone index. A list such as 203.0.113.1, 198.51.100.7, a padded value, fe80::1%eth0 and 01.2.3.4 are now skipped, and the Engine tries the next client IP key. Pass one address in each value (#130, ip-intelligence).
  8. Property lists are read only. IFlowElement.Properties and IAspectEngine.Properties return a read only list, and code that changes the list gets a NotSupportedException. Copy the list first, for example new List<IElementPropertyMetaData>(element.Properties) (#99, pipeline).
  9. The JavaScript Builder needs a Sequence Element. Without one it renders sequence 1 and an empty session id, whatever the request carried. The web integration already adds one (#132, pipeline).
  10. Settings that were accepted now stop the Pipeline build. These are a JavaScript Builder protocol other than http or https (#59) and an object name that the script cannot declare, such as window, document or location (#123, pipeline).
  11. Evidence named resource or license no longer replaces the configured key. The Cloud Request Engine leaves out Evidence named resource, license, licence or values. Set the keys with SetResourceKey and SetLicenseKey (#124, pipeline).
  12. A .NET 10 web application may have to raise two package versions. This applies only to an application that targets net10.0, uses FiftyOne.Pipeline.Web directly or through another package, and names Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation or Microsoft.Extensions.FileProviders.Embedded in its own project file at a version below 10.0.14. The new net10.0 build of FiftyOne.Pipeline.Web needs both at 10.0.14 or later, where the build a .NET 10 application loaded before needed 6.0.15. NuGet then stops the restore with NU1605, "Detected package downgrade", which the .NET SDK treats as an error. Change both versions in the project file to 10.0.14 or later, or remove the two references so that FiftyOne.Pipeline.Web brings them in. An application that targets net8.0, or that names neither package, needs no change (#95, Pipeline).
  13. An Engine built with no Property names keeps the first Data File's Properties. A Property that only a later Data File holds reads as unavailable until the Engine is built again (#137, device-detection and ip-intelligence).
  14. A Property with no value gives a message. NoValueMessage, and the JSON nullreason, of an on-premise Property with no value hold "None of the results contain a value for the requested property.", where they were null (#116, device-detection and ip-intelligence).
  15. The agent signature element accepts only the eight Evidence keys its specification names. A signature that covers any other header is reported Unverified with the reason ComponentUnavailable (#106, pipeline).
  16. A 51Did with white space inside it, or with characters from both base64 alphabets, is refused. FodId.TryParse reports InvalidBase64, and the string constructor and FodId.FromBase64 throw FormatException (#85, pipeline).
  17. The Usage Sharing builder checks its back-off settings. SetFailuresWindowSeconds, SetInitialRecoveryDelaySeconds, SetMaxRecoveryDelaySeconds and SetRecoveryMultiplier reject a value the back-off cannot use. RecoverySeconds, UseExponentialBackoff and CreateRecoveryStrategy on ShareUsageBuilderBase are obsolete (#88, pipeline).
  18. _51DEGREES_CLOUD_ENDPOINT replaces FOD_CLOUD_API_URL, which still works in this release. When no endpoint is set in code or configuration, CloudRequestEngineBuilder and DidClient read _51DEGREES_CLOUD_ENDPOINT, and read FOD_CLOUD_API_URL only when the new name is unset or empty. The first use of the old name in a process is reported as deprecated, as a warning through the builder's logger, and by DidClient through System.Diagnostics.Trace. Constants.FOD_CLOUD_API_URL and DidClient.EndpointEnvironmentVariable still hold FOD_CLOUD_API_URL and compile with an obsolete warning, and Constants.CLOUD_ENDPOINT_ENV_VAR and the new DidClient.CloudEndpointEnvironmentVariable hold the new name. Set _51DEGREES_CLOUD_ENDPOINT to the same value as the old name (#131, #143, pipeline). The examples, tests and CI scripts also read every old name in the table under "Environment variables" as a deprecated name, when its new name is unset or empty (#144).

What changes

Web integration and client-side caching

  • A request whose If-None-Match matches gets 304 for GET and HEAD, and 412 for any other method, as RFC ...
Read more

location/4.5.197

Choose a tag to compare

@Automation51D Automation51D released this 13 Nov 01:58
8b3220b

This release moves .NET toward one behavior across every 51Degrees language. Each element it changes now follows the published 51Degrees specifications, which in turn follow the RFCs they cite, so that the same input gives the same answer in .NET, Java, Node.js, Python, PHP, Go, Rust and C. .NET was the reference the other languages were aligned to, so many of its changes are small. The native libraries take the C library release 51degrees-cxx 4.5.105. Each change names the package family it is in.

This release adds .NET 10. Every package gains a net10.0 build and keeps the builds it had, so a .NET 10 application now loads code built for .NET 10, where it loaded the .NET 8 or .NET Standard 2.0 build before. One kind of .NET 10 web application has to raise two package versions before it will restore, which is set out under "Before you upgrade".

Before you upgrade

  1. The client-side ETag is a weak entity tag. The JavaScript and JSON endpoints send W/"...", where they sent a bare number, and compare If-None-Match weakly, as RFC 9110 section 8.8.3 and section 13.1.2 ask. Code that reads the ETag as a number needs to allow for W/ and the double quotes (#96, pipeline).
  2. Web integration options in a configuration file now take effect. On ASP.NET Core nothing bound PipelineWebIntegrationOptions to the configuration, so the defaults always applied. A file that sets ClientSideEvidenceEnabled or UseSetHeaderProperties to false now turns that feature off, so check both values (#115, pipeline).
  3. Usage Sharing accepts no Evidence. It reads the web request instead, so a Pipeline that holds it no longer accepts every header. A Flow Element of your own that read a header it did not declare must name the key in its EvidenceKeyFilter, or read the request from the new server.http-request Evidence value (#100, pipeline).
  4. An application that builds its own Evidence has to give Usage Sharing the web request. This applies to an application that adds a value to Evidence only when EvidenceKeyFilter on the Pipeline or the Flow Data includes its key. An application that uses the web integration has nothing to change. Up to pipeline 4.5.129 Usage Sharing accepted the headers it shares, so that check kept them. Usage Sharing now accepts none, so the same check drops every header that no other Flow Element reads, and those headers stop being shared. Add the request to the Flow Data under Constants.EVIDENCE_HTTPREQUEST_KEY in FiftyOne.Pipeline.Core, which is server.http-request. The value is an IReadOnlyDictionary<string, object> that holds each value of the request under the key it would have as Evidence, such as header.user-agent, cookie.51D_ScreenPixelsWidth, query.name and server.client-ip. Usage Sharing shares every Evidence value in the Flow Data, then each value of that dictionary whose key the Evidence does not hold. Its rules still apply, so the Cookie header, a blocked header and a cookie whose name does not start 51D_ are left out. The dictionary itself is never shared, is not sent to the cloud service and takes no part in a cache key. On ASP.NET Core, IWebRequestEvidenceService.AddEvidenceFromRequest in FiftyOne.Pipeline.Web adds the request for you (#100, pipeline).
  5. On .NET Framework, session Evidence is renamed. A session value is session.<name> and the session object is session.session, where they were <name> and session (#100, pipeline).
  6. IpiOnPremiseEngineBuilder defaults to the Balanced performance profile. With no profile set it loaded the whole Data File into memory. Call SetPerformanceProfile(PerformanceProfiles.MaxPerformance) to keep the old behavior. IpiOnPremisePipelineBuilder already used Balanced (#102, ip-intelligence).
  7. A client IP value is read only when all of it is one address. .NET read the first entry of a list, trimmed white space and dropped a zone index. A list such as 203.0.113.1, 198.51.100.7, a padded value, fe80::1%eth0 and 01.2.3.4 are now skipped, and the Engine tries the next client IP key. Pass one address in each value (#130, ip-intelligence).
  8. Property lists are read only. IFlowElement.Properties and IAspectEngine.Properties return a read only list, and code that changes the list gets a NotSupportedException. Copy the list first, for example new List<IElementPropertyMetaData>(element.Properties) (#99, pipeline).
  9. The JavaScript Builder needs a Sequence Element. Without one it renders sequence 1 and an empty session id, whatever the request carried. The web integration already adds one (#132, pipeline).
  10. Settings that were accepted now stop the Pipeline build. These are a JavaScript Builder protocol other than http or https (#59) and an object name that the script cannot declare, such as window, document or location (#123, pipeline).
  11. Evidence named resource or license no longer replaces the configured key. The Cloud Request Engine leaves out Evidence named resource, license, licence or values. Set the keys with SetResourceKey and SetLicenseKey (#124, pipeline).
  12. A .NET 10 web application may have to raise two package versions. This applies only to an application that targets net10.0, uses FiftyOne.Pipeline.Web directly or through another package, and names Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation or Microsoft.Extensions.FileProviders.Embedded in its own project file at a version below 10.0.14. The new net10.0 build of FiftyOne.Pipeline.Web needs both at 10.0.14 or later, where the build a .NET 10 application loaded before needed 6.0.15. NuGet then stops the restore with NU1605, "Detected package downgrade", which the .NET SDK treats as an error. Change both versions in the project file to 10.0.14 or later, or remove the two references so that FiftyOne.Pipeline.Web brings them in. An application that targets net8.0, or that names neither package, needs no change (#95, Pipeline).
  13. An Engine built with no Property names keeps the first Data File's Properties. A Property that only a later Data File holds reads as unavailable until the Engine is built again (#137, device-detection and ip-intelligence).
  14. A Property with no value gives a message. NoValueMessage, and the JSON nullreason, of an on-premise Property with no value hold "None of the results contain a value for the requested property.", where they were null (#116, device-detection and ip-intelligence).
  15. The agent signature element accepts only the eight Evidence keys its specification names. A signature that covers any other header is reported Unverified with the reason ComponentUnavailable (#106, pipeline).
  16. A 51Did with white space inside it, or with characters from both base64 alphabets, is refused. FodId.TryParse reports InvalidBase64, and the string constructor and FodId.FromBase64 throw FormatException (#85, pipeline).
  17. The Usage Sharing builder checks its back-off settings. SetFailuresWindowSeconds, SetInitialRecoveryDelaySeconds, SetMaxRecoveryDelaySeconds and SetRecoveryMultiplier reject a value the back-off cannot use. RecoverySeconds, UseExponentialBackoff and CreateRecoveryStrategy on ShareUsageBuilderBase are obsolete (#88, pipeline).
  18. _51DEGREES_CLOUD_ENDPOINT replaces FOD_CLOUD_API_URL, which still works in this release. When no endpoint is set in code or configuration, CloudRequestEngineBuilder and DidClient read _51DEGREES_CLOUD_ENDPOINT, and read FOD_CLOUD_API_URL only when the new name is unset or empty. The first use of the old name in a process is reported as deprecated, as a warning through the builder's logger, and by DidClient through System.Diagnostics.Trace. Constants.FOD_CLOUD_API_URL and DidClient.EndpointEnvironmentVariable still hold FOD_CLOUD_API_URL and compile with an obsolete warning, and Constants.CLOUD_ENDPOINT_ENV_VAR and the new DidClient.CloudEndpointEnvironmentVariable hold the new name. Set _51DEGREES_CLOUD_ENDPOINT to the same value as the old name (#131, #143, pipeline). The examples, tests and CI scripts also read every old name in the table under "Environment variables" as a deprecated name, when its new name is unset or empty (#144).

What changes

Web integration and client-side caching

  • A request whose If-None-Match matches gets 304 for GET and HEAD, and 412 for any other method, as RFC ...
Read more

ip-intelligence/4.5.156

Choose a tag to compare

@Automation51D Automation51D released this 13 Nov 01:57
8b3220b

This release moves .NET toward one behavior across every 51Degrees language. Each element it changes now follows the published 51Degrees specifications, which in turn follow the RFCs they cite, so that the same input gives the same answer in .NET, Java, Node.js, Python, PHP, Go, Rust and C. .NET was the reference the other languages were aligned to, so many of its changes are small. The native libraries take the C library release 51degrees-cxx 4.5.105. Each change names the package family it is in.

This release adds .NET 10. Every package gains a net10.0 build and keeps the builds it had, so a .NET 10 application now loads code built for .NET 10, where it loaded the .NET 8 or .NET Standard 2.0 build before. One kind of .NET 10 web application has to raise two package versions before it will restore, which is set out under "Before you upgrade".

Before you upgrade

  1. The client-side ETag is a weak entity tag. The JavaScript and JSON endpoints send W/"...", where they sent a bare number, and compare If-None-Match weakly, as RFC 9110 section 8.8.3 and section 13.1.2 ask. Code that reads the ETag as a number needs to allow for W/ and the double quotes (#96, pipeline).
  2. Web integration options in a configuration file now take effect. On ASP.NET Core nothing bound PipelineWebIntegrationOptions to the configuration, so the defaults always applied. A file that sets ClientSideEvidenceEnabled or UseSetHeaderProperties to false now turns that feature off, so check both values (#115, pipeline).
  3. Usage Sharing accepts no Evidence. It reads the web request instead, so a Pipeline that holds it no longer accepts every header. A Flow Element of your own that read a header it did not declare must name the key in its EvidenceKeyFilter, or read the request from the new server.http-request Evidence value (#100, pipeline).
  4. An application that builds its own Evidence has to give Usage Sharing the web request. This applies to an application that adds a value to Evidence only when EvidenceKeyFilter on the Pipeline or the Flow Data includes its key. An application that uses the web integration has nothing to change. Up to pipeline 4.5.129 Usage Sharing accepted the headers it shares, so that check kept them. Usage Sharing now accepts none, so the same check drops every header that no other Flow Element reads, and those headers stop being shared. Add the request to the Flow Data under Constants.EVIDENCE_HTTPREQUEST_KEY in FiftyOne.Pipeline.Core, which is server.http-request. The value is an IReadOnlyDictionary<string, object> that holds each value of the request under the key it would have as Evidence, such as header.user-agent, cookie.51D_ScreenPixelsWidth, query.name and server.client-ip. Usage Sharing shares every Evidence value in the Flow Data, then each value of that dictionary whose key the Evidence does not hold. Its rules still apply, so the Cookie header, a blocked header and a cookie whose name does not start 51D_ are left out. The dictionary itself is never shared, is not sent to the cloud service and takes no part in a cache key. On ASP.NET Core, IWebRequestEvidenceService.AddEvidenceFromRequest in FiftyOne.Pipeline.Web adds the request for you (#100, pipeline).
  5. On .NET Framework, session Evidence is renamed. A session value is session.<name> and the session object is session.session, where they were <name> and session (#100, pipeline).
  6. IpiOnPremiseEngineBuilder defaults to the Balanced performance profile. With no profile set it loaded the whole Data File into memory. Call SetPerformanceProfile(PerformanceProfiles.MaxPerformance) to keep the old behavior. IpiOnPremisePipelineBuilder already used Balanced (#102, ip-intelligence).
  7. A client IP value is read only when all of it is one address. .NET read the first entry of a list, trimmed white space and dropped a zone index. A list such as 203.0.113.1, 198.51.100.7, a padded value, fe80::1%eth0 and 01.2.3.4 are now skipped, and the Engine tries the next client IP key. Pass one address in each value (#130, ip-intelligence).
  8. Property lists are read only. IFlowElement.Properties and IAspectEngine.Properties return a read only list, and code that changes the list gets a NotSupportedException. Copy the list first, for example new List<IElementPropertyMetaData>(element.Properties) (#99, pipeline).
  9. The JavaScript Builder needs a Sequence Element. Without one it renders sequence 1 and an empty session id, whatever the request carried. The web integration already adds one (#132, pipeline).
  10. Settings that were accepted now stop the Pipeline build. These are a JavaScript Builder protocol other than http or https (#59) and an object name that the script cannot declare, such as window, document or location (#123, pipeline).
  11. Evidence named resource or license no longer replaces the configured key. The Cloud Request Engine leaves out Evidence named resource, license, licence or values. Set the keys with SetResourceKey and SetLicenseKey (#124, pipeline).
  12. A .NET 10 web application may have to raise two package versions. This applies only to an application that targets net10.0, uses FiftyOne.Pipeline.Web directly or through another package, and names Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation or Microsoft.Extensions.FileProviders.Embedded in its own project file at a version below 10.0.14. The new net10.0 build of FiftyOne.Pipeline.Web needs both at 10.0.14 or later, where the build a .NET 10 application loaded before needed 6.0.15. NuGet then stops the restore with NU1605, "Detected package downgrade", which the .NET SDK treats as an error. Change both versions in the project file to 10.0.14 or later, or remove the two references so that FiftyOne.Pipeline.Web brings them in. An application that targets net8.0, or that names neither package, needs no change (#95, Pipeline).
  13. An Engine built with no Property names keeps the first Data File's Properties. A Property that only a later Data File holds reads as unavailable until the Engine is built again (#137, device-detection and ip-intelligence).
  14. A Property with no value gives a message. NoValueMessage, and the JSON nullreason, of an on-premise Property with no value hold "None of the results contain a value for the requested property.", where they were null (#116, device-detection and ip-intelligence).
  15. The agent signature element accepts only the eight Evidence keys its specification names. A signature that covers any other header is reported Unverified with the reason ComponentUnavailable (#106, pipeline).
  16. A 51Did with white space inside it, or with characters from both base64 alphabets, is refused. FodId.TryParse reports InvalidBase64, and the string constructor and FodId.FromBase64 throw FormatException (#85, pipeline).
  17. The Usage Sharing builder checks its back-off settings. SetFailuresWindowSeconds, SetInitialRecoveryDelaySeconds, SetMaxRecoveryDelaySeconds and SetRecoveryMultiplier reject a value the back-off cannot use. RecoverySeconds, UseExponentialBackoff and CreateRecoveryStrategy on ShareUsageBuilderBase are obsolete (#88, pipeline).
  18. _51DEGREES_CLOUD_ENDPOINT replaces FOD_CLOUD_API_URL, which still works in this release. When no endpoint is set in code or configuration, CloudRequestEngineBuilder and DidClient read _51DEGREES_CLOUD_ENDPOINT, and read FOD_CLOUD_API_URL only when the new name is unset or empty. The first use of the old name in a process is reported as deprecated, as a warning through the builder's logger, and by DidClient through System.Diagnostics.Trace. Constants.FOD_CLOUD_API_URL and DidClient.EndpointEnvironmentVariable still hold FOD_CLOUD_API_URL and compile with an obsolete warning, and Constants.CLOUD_ENDPOINT_ENV_VAR and the new DidClient.CloudEndpointEnvironmentVariable hold the new name. Set _51DEGREES_CLOUD_ENDPOINT to the same value as the old name (#131, #143, pipeline). The examples, tests and CI scripts also read every old name in the table under "Environment variables" as a deprecated name, when its new name is unset or empty (#144).

What changes

Web integration and client-side caching

  • A request whose If-None-Match matches gets 304 for GET and HEAD, and 412 for any other method, as RFC ...
Read more

device-detection/4.5.181

Choose a tag to compare

@Automation51D Automation51D released this 13 Nov 01:57
8b3220b

This release moves .NET toward one behavior across every 51Degrees language. Each element it changes now follows the published 51Degrees specifications, which in turn follow the RFCs they cite, so that the same input gives the same answer in .NET, Java, Node.js, Python, PHP, Go, Rust and C. .NET was the reference the other languages were aligned to, so many of its changes are small. The native libraries take the C library release 51degrees-cxx 4.5.105. Each change names the package family it is in.

This release adds .NET 10. Every package gains a net10.0 build and keeps the builds it had, so a .NET 10 application now loads code built for .NET 10, where it loaded the .NET 8 or .NET Standard 2.0 build before. One kind of .NET 10 web application has to raise two package versions before it will restore, which is set out under "Before you upgrade".

Before you upgrade

  1. The client-side ETag is a weak entity tag. The JavaScript and JSON endpoints send W/"...", where they sent a bare number, and compare If-None-Match weakly, as RFC 9110 section 8.8.3 and section 13.1.2 ask. Code that reads the ETag as a number needs to allow for W/ and the double quotes (#96, pipeline).
  2. Web integration options in a configuration file now take effect. On ASP.NET Core nothing bound PipelineWebIntegrationOptions to the configuration, so the defaults always applied. A file that sets ClientSideEvidenceEnabled or UseSetHeaderProperties to false now turns that feature off, so check both values (#115, pipeline).
  3. Usage Sharing accepts no Evidence. It reads the web request instead, so a Pipeline that holds it no longer accepts every header. A Flow Element of your own that read a header it did not declare must name the key in its EvidenceKeyFilter, or read the request from the new server.http-request Evidence value (#100, pipeline).
  4. An application that builds its own Evidence has to give Usage Sharing the web request. This applies to an application that adds a value to Evidence only when EvidenceKeyFilter on the Pipeline or the Flow Data includes its key. An application that uses the web integration has nothing to change. Up to pipeline 4.5.129 Usage Sharing accepted the headers it shares, so that check kept them. Usage Sharing now accepts none, so the same check drops every header that no other Flow Element reads, and those headers stop being shared. Add the request to the Flow Data under Constants.EVIDENCE_HTTPREQUEST_KEY in FiftyOne.Pipeline.Core, which is server.http-request. The value is an IReadOnlyDictionary<string, object> that holds each value of the request under the key it would have as Evidence, such as header.user-agent, cookie.51D_ScreenPixelsWidth, query.name and server.client-ip. Usage Sharing shares every Evidence value in the Flow Data, then each value of that dictionary whose key the Evidence does not hold. Its rules still apply, so the Cookie header, a blocked header and a cookie whose name does not start 51D_ are left out. The dictionary itself is never shared, is not sent to the cloud service and takes no part in a cache key. On ASP.NET Core, IWebRequestEvidenceService.AddEvidenceFromRequest in FiftyOne.Pipeline.Web adds the request for you (#100, pipeline).
  5. On .NET Framework, session Evidence is renamed. A session value is session.<name> and the session object is session.session, where they were <name> and session (#100, pipeline).
  6. IpiOnPremiseEngineBuilder defaults to the Balanced performance profile. With no profile set it loaded the whole Data File into memory. Call SetPerformanceProfile(PerformanceProfiles.MaxPerformance) to keep the old behavior. IpiOnPremisePipelineBuilder already used Balanced (#102, ip-intelligence).
  7. A client IP value is read only when all of it is one address. .NET read the first entry of a list, trimmed white space and dropped a zone index. A list such as 203.0.113.1, 198.51.100.7, a padded value, fe80::1%eth0 and 01.2.3.4 are now skipped, and the Engine tries the next client IP key. Pass one address in each value (#130, ip-intelligence).
  8. Property lists are read only. IFlowElement.Properties and IAspectEngine.Properties return a read only list, and code that changes the list gets a NotSupportedException. Copy the list first, for example new List<IElementPropertyMetaData>(element.Properties) (#99, pipeline).
  9. The JavaScript Builder needs a Sequence Element. Without one it renders sequence 1 and an empty session id, whatever the request carried. The web integration already adds one (#132, pipeline).
  10. Settings that were accepted now stop the Pipeline build. These are a JavaScript Builder protocol other than http or https (#59) and an object name that the script cannot declare, such as window, document or location (#123, pipeline).
  11. Evidence named resource or license no longer replaces the configured key. The Cloud Request Engine leaves out Evidence named resource, license, licence or values. Set the keys with SetResourceKey and SetLicenseKey (#124, pipeline).
  12. A .NET 10 web application may have to raise two package versions. This applies only to an application that targets net10.0, uses FiftyOne.Pipeline.Web directly or through another package, and names Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation or Microsoft.Extensions.FileProviders.Embedded in its own project file at a version below 10.0.14. The new net10.0 build of FiftyOne.Pipeline.Web needs both at 10.0.14 or later, where the build a .NET 10 application loaded before needed 6.0.15. NuGet then stops the restore with NU1605, "Detected package downgrade", which the .NET SDK treats as an error. Change both versions in the project file to 10.0.14 or later, or remove the two references so that FiftyOne.Pipeline.Web brings them in. An application that targets net8.0, or that names neither package, needs no change (#95, Pipeline).
  13. An Engine built with no Property names keeps the first Data File's Properties. A Property that only a later Data File holds reads as unavailable until the Engine is built again (#137, device-detection and ip-intelligence).
  14. A Property with no value gives a message. NoValueMessage, and the JSON nullreason, of an on-premise Property with no value hold "None of the results contain a value for the requested property.", where they were null (#116, device-detection and ip-intelligence).
  15. The agent signature element accepts only the eight Evidence keys its specification names. A signature that covers any other header is reported Unverified with the reason ComponentUnavailable (#106, pipeline).
  16. A 51Did with white space inside it, or with characters from both base64 alphabets, is refused. FodId.TryParse reports InvalidBase64, and the string constructor and FodId.FromBase64 throw FormatException (#85, pipeline).
  17. The Usage Sharing builder checks its back-off settings. SetFailuresWindowSeconds, SetInitialRecoveryDelaySeconds, SetMaxRecoveryDelaySeconds and SetRecoveryMultiplier reject a value the back-off cannot use. RecoverySeconds, UseExponentialBackoff and CreateRecoveryStrategy on ShareUsageBuilderBase are obsolete (#88, pipeline).
  18. _51DEGREES_CLOUD_ENDPOINT replaces FOD_CLOUD_API_URL, which still works in this release. When no endpoint is set in code or configuration, CloudRequestEngineBuilder and DidClient read _51DEGREES_CLOUD_ENDPOINT, and read FOD_CLOUD_API_URL only when the new name is unset or empty. The first use of the old name in a process is reported as deprecated, as a warning through the builder's logger, and by DidClient through System.Diagnostics.Trace. Constants.FOD_CLOUD_API_URL and DidClient.EndpointEnvironmentVariable still hold FOD_CLOUD_API_URL and compile with an obsolete warning, and Constants.CLOUD_ENDPOINT_ENV_VAR and the new DidClient.CloudEndpointEnvironmentVariable hold the new name. Set _51DEGREES_CLOUD_ENDPOINT to the same value as the old name (#131, #143, pipeline). The examples, tests and CI scripts also read every old name in the table under "Environment variables" as a deprecated name, when its new name is unset or empty (#144).

What changes

Web integration and client-side caching

  • A request whose If-None-Match matches gets 304 for GET and HEAD, and 412 for any other method, as RFC ...
Read more

common/5.1.10

Choose a tag to compare

@Automation51D Automation51D released this 13 Nov 01:57
8b3220b

This release moves .NET toward one behavior across every 51Degrees language. Each element it changes now follows the published 51Degrees specifications, which in turn follow the RFCs they cite, so that the same input gives the same answer in .NET, Java, Node.js, Python, PHP, Go, Rust and C. .NET was the reference the other languages were aligned to, so many of its changes are small. The native libraries take the C library release 51degrees-cxx 4.5.105. Each change names the package family it is in.

This release adds .NET 10. Every package gains a net10.0 build and keeps the builds it had, so a .NET 10 application now loads code built for .NET 10, where it loaded the .NET 8 or .NET Standard 2.0 build before. One kind of .NET 10 web application has to raise two package versions before it will restore, which is set out under "Before you upgrade".

Before you upgrade

  1. The client-side ETag is a weak entity tag. The JavaScript and JSON endpoints send W/"...", where they sent a bare number, and compare If-None-Match weakly, as RFC 9110 section 8.8.3 and section 13.1.2 ask. Code that reads the ETag as a number needs to allow for W/ and the double quotes (#96, pipeline).
  2. Web integration options in a configuration file now take effect. On ASP.NET Core nothing bound PipelineWebIntegrationOptions to the configuration, so the defaults always applied. A file that sets ClientSideEvidenceEnabled or UseSetHeaderProperties to false now turns that feature off, so check both values (#115, pipeline).
  3. Usage Sharing accepts no Evidence. It reads the web request instead, so a Pipeline that holds it no longer accepts every header. A Flow Element of your own that read a header it did not declare must name the key in its EvidenceKeyFilter, or read the request from the new server.http-request Evidence value (#100, pipeline).
  4. An application that builds its own Evidence has to give Usage Sharing the web request. This applies to an application that adds a value to Evidence only when EvidenceKeyFilter on the Pipeline or the Flow Data includes its key. An application that uses the web integration has nothing to change. Up to pipeline 4.5.129 Usage Sharing accepted the headers it shares, so that check kept them. Usage Sharing now accepts none, so the same check drops every header that no other Flow Element reads, and those headers stop being shared. Add the request to the Flow Data under Constants.EVIDENCE_HTTPREQUEST_KEY in FiftyOne.Pipeline.Core, which is server.http-request. The value is an IReadOnlyDictionary<string, object> that holds each value of the request under the key it would have as Evidence, such as header.user-agent, cookie.51D_ScreenPixelsWidth, query.name and server.client-ip. Usage Sharing shares every Evidence value in the Flow Data, then each value of that dictionary whose key the Evidence does not hold. Its rules still apply, so the Cookie header, a blocked header and a cookie whose name does not start 51D_ are left out. The dictionary itself is never shared, is not sent to the cloud service and takes no part in a cache key. On ASP.NET Core, IWebRequestEvidenceService.AddEvidenceFromRequest in FiftyOne.Pipeline.Web adds the request for you (#100, pipeline).
  5. On .NET Framework, session Evidence is renamed. A session value is session.<name> and the session object is session.session, where they were <name> and session (#100, pipeline).
  6. IpiOnPremiseEngineBuilder defaults to the Balanced performance profile. With no profile set it loaded the whole Data File into memory. Call SetPerformanceProfile(PerformanceProfiles.MaxPerformance) to keep the old behavior. IpiOnPremisePipelineBuilder already used Balanced (#102, ip-intelligence).
  7. A client IP value is read only when all of it is one address. .NET read the first entry of a list, trimmed white space and dropped a zone index. A list such as 203.0.113.1, 198.51.100.7, a padded value, fe80::1%eth0 and 01.2.3.4 are now skipped, and the Engine tries the next client IP key. Pass one address in each value (#130, ip-intelligence).
  8. Property lists are read only. IFlowElement.Properties and IAspectEngine.Properties return a read only list, and code that changes the list gets a NotSupportedException. Copy the list first, for example new List<IElementPropertyMetaData>(element.Properties) (#99, pipeline).
  9. The JavaScript Builder needs a Sequence Element. Without one it renders sequence 1 and an empty session id, whatever the request carried. The web integration already adds one (#132, pipeline).
  10. Settings that were accepted now stop the Pipeline build. These are a JavaScript Builder protocol other than http or https (#59) and an object name that the script cannot declare, such as window, document or location (#123, pipeline).
  11. Evidence named resource or license no longer replaces the configured key. The Cloud Request Engine leaves out Evidence named resource, license, licence or values. Set the keys with SetResourceKey and SetLicenseKey (#124, pipeline).
  12. A .NET 10 web application may have to raise two package versions. This applies only to an application that targets net10.0, uses FiftyOne.Pipeline.Web directly or through another package, and names Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation or Microsoft.Extensions.FileProviders.Embedded in its own project file at a version below 10.0.14. The new net10.0 build of FiftyOne.Pipeline.Web needs both at 10.0.14 or later, where the build a .NET 10 application loaded before needed 6.0.15. NuGet then stops the restore with NU1605, "Detected package downgrade", which the .NET SDK treats as an error. Change both versions in the project file to 10.0.14 or later, or remove the two references so that FiftyOne.Pipeline.Web brings them in. An application that targets net8.0, or that names neither package, needs no change (#95, Pipeline).
  13. An Engine built with no Property names keeps the first Data File's Properties. A Property that only a later Data File holds reads as unavailable until the Engine is built again (#137, device-detection and ip-intelligence).
  14. A Property with no value gives a message. NoValueMessage, and the JSON nullreason, of an on-premise Property with no value hold "None of the results contain a value for the requested property.", where they were null (#116, device-detection and ip-intelligence).
  15. The agent signature element accepts only the eight Evidence keys its specification names. A signature that covers any other header is reported Unverified with the reason ComponentUnavailable (#106, pipeline).
  16. A 51Did with white space inside it, or with characters from both base64 alphabets, is refused. FodId.TryParse reports InvalidBase64, and the string constructor and FodId.FromBase64 throw FormatException (#85, pipeline).
  17. The Usage Sharing builder checks its back-off settings. SetFailuresWindowSeconds, SetInitialRecoveryDelaySeconds, SetMaxRecoveryDelaySeconds and SetRecoveryMultiplier reject a value the back-off cannot use. RecoverySeconds, UseExponentialBackoff and CreateRecoveryStrategy on ShareUsageBuilderBase are obsolete (#88, pipeline).
  18. _51DEGREES_CLOUD_ENDPOINT replaces FOD_CLOUD_API_URL, which still works in this release. When no endpoint is set in code or configuration, CloudRequestEngineBuilder and DidClient read _51DEGREES_CLOUD_ENDPOINT, and read FOD_CLOUD_API_URL only when the new name is unset or empty. The first use of the old name in a process is reported as deprecated, as a warning through the builder's logger, and by DidClient through System.Diagnostics.Trace. Constants.FOD_CLOUD_API_URL and DidClient.EndpointEnvironmentVariable still hold FOD_CLOUD_API_URL and compile with an obsolete warning, and Constants.CLOUD_ENDPOINT_ENV_VAR and the new DidClient.CloudEndpointEnvironmentVariable hold the new name. Set _51DEGREES_CLOUD_ENDPOINT to the same value as the old name (#131, #143, pipeline). The examples, tests and CI scripts also read every old name in the table under "Environment variables" as a deprecated name, when its new name is unset or empty (#144).

What changes

Web integration and client-side caching

  • A request whose If-None-Match matches gets 304 for GET and HEAD, and 412 for any other method, as RFC ...
Read more

caching/4.5.4

Choose a tag to compare

@Automation51D Automation51D released this 13 Nov 01:57
8b3220b

This release moves .NET toward one behavior across every 51Degrees language. Each element it changes now follows the published 51Degrees specifications, which in turn follow the RFCs they cite, so that the same input gives the same answer in .NET, Java, Node.js, Python, PHP, Go, Rust and C. .NET was the reference the other languages were aligned to, so many of its changes are small. The native libraries take the C library release 51degrees-cxx 4.5.105. Each change names the package family it is in.

This release adds .NET 10. Every package gains a net10.0 build and keeps the builds it had, so a .NET 10 application now loads code built for .NET 10, where it loaded the .NET 8 or .NET Standard 2.0 build before. One kind of .NET 10 web application has to raise two package versions before it will restore, which is set out under "Before you upgrade".

Before you upgrade

  1. The client-side ETag is a weak entity tag. The JavaScript and JSON endpoints send W/"...", where they sent a bare number, and compare If-None-Match weakly, as RFC 9110 section 8.8.3 and section 13.1.2 ask. Code that reads the ETag as a number needs to allow for W/ and the double quotes (#96, pipeline).
  2. Web integration options in a configuration file now take effect. On ASP.NET Core nothing bound PipelineWebIntegrationOptions to the configuration, so the defaults always applied. A file that sets ClientSideEvidenceEnabled or UseSetHeaderProperties to false now turns that feature off, so check both values (#115, pipeline).
  3. Usage Sharing accepts no Evidence. It reads the web request instead, so a Pipeline that holds it no longer accepts every header. A Flow Element of your own that read a header it did not declare must name the key in its EvidenceKeyFilter, or read the request from the new server.http-request Evidence value (#100, pipeline).
  4. An application that builds its own Evidence has to give Usage Sharing the web request. This applies to an application that adds a value to Evidence only when EvidenceKeyFilter on the Pipeline or the Flow Data includes its key. An application that uses the web integration has nothing to change. Up to pipeline 4.5.129 Usage Sharing accepted the headers it shares, so that check kept them. Usage Sharing now accepts none, so the same check drops every header that no other Flow Element reads, and those headers stop being shared. Add the request to the Flow Data under Constants.EVIDENCE_HTTPREQUEST_KEY in FiftyOne.Pipeline.Core, which is server.http-request. The value is an IReadOnlyDictionary<string, object> that holds each value of the request under the key it would have as Evidence, such as header.user-agent, cookie.51D_ScreenPixelsWidth, query.name and server.client-ip. Usage Sharing shares every Evidence value in the Flow Data, then each value of that dictionary whose key the Evidence does not hold. Its rules still apply, so the Cookie header, a blocked header and a cookie whose name does not start 51D_ are left out. The dictionary itself is never shared, is not sent to the cloud service and takes no part in a cache key. On ASP.NET Core, IWebRequestEvidenceService.AddEvidenceFromRequest in FiftyOne.Pipeline.Web adds the request for you (#100, pipeline).
  5. On .NET Framework, session Evidence is renamed. A session value is session.<name> and the session object is session.session, where they were <name> and session (#100, pipeline).
  6. IpiOnPremiseEngineBuilder defaults to the Balanced performance profile. With no profile set it loaded the whole Data File into memory. Call SetPerformanceProfile(PerformanceProfiles.MaxPerformance) to keep the old behavior. IpiOnPremisePipelineBuilder already used Balanced (#102, ip-intelligence).
  7. A client IP value is read only when all of it is one address. .NET read the first entry of a list, trimmed white space and dropped a zone index. A list such as 203.0.113.1, 198.51.100.7, a padded value, fe80::1%eth0 and 01.2.3.4 are now skipped, and the Engine tries the next client IP key. Pass one address in each value (#130, ip-intelligence).
  8. Property lists are read only. IFlowElement.Properties and IAspectEngine.Properties return a read only list, and code that changes the list gets a NotSupportedException. Copy the list first, for example new List<IElementPropertyMetaData>(element.Properties) (#99, pipeline).
  9. The JavaScript Builder needs a Sequence Element. Without one it renders sequence 1 and an empty session id, whatever the request carried. The web integration already adds one (#132, pipeline).
  10. Settings that were accepted now stop the Pipeline build. These are a JavaScript Builder protocol other than http or https (#59) and an object name that the script cannot declare, such as window, document or location (#123, pipeline).
  11. Evidence named resource or license no longer replaces the configured key. The Cloud Request Engine leaves out Evidence named resource, license, licence or values. Set the keys with SetResourceKey and SetLicenseKey (#124, pipeline).
  12. A .NET 10 web application may have to raise two package versions. This applies only to an application that targets net10.0, uses FiftyOne.Pipeline.Web directly or through another package, and names Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation or Microsoft.Extensions.FileProviders.Embedded in its own project file at a version below 10.0.14. The new net10.0 build of FiftyOne.Pipeline.Web needs both at 10.0.14 or later, where the build a .NET 10 application loaded before needed 6.0.15. NuGet then stops the restore with NU1605, "Detected package downgrade", which the .NET SDK treats as an error. Change both versions in the project file to 10.0.14 or later, or remove the two references so that FiftyOne.Pipeline.Web brings them in. An application that targets net8.0, or that names neither package, needs no change (#95, Pipeline).
  13. An Engine built with no Property names keeps the first Data File's Properties. A Property that only a later Data File holds reads as unavailable until the Engine is built again (#137, device-detection and ip-intelligence).
  14. A Property with no value gives a message. NoValueMessage, and the JSON nullreason, of an on-premise Property with no value hold "None of the results contain a value for the requested property.", where they were null (#116, device-detection and ip-intelligence).
  15. The agent signature element accepts only the eight Evidence keys its specification names. A signature that covers any other header is reported Unverified with the reason ComponentUnavailable (#106, pipeline).
  16. A 51Did with white space inside it, or with characters from both base64 alphabets, is refused. FodId.TryParse reports InvalidBase64, and the string constructor and FodId.FromBase64 throw FormatException (#85, pipeline).
  17. The Usage Sharing builder checks its back-off settings. SetFailuresWindowSeconds, SetInitialRecoveryDelaySeconds, SetMaxRecoveryDelaySeconds and SetRecoveryMultiplier reject a value the back-off cannot use. RecoverySeconds, UseExponentialBackoff and CreateRecoveryStrategy on ShareUsageBuilderBase are obsolete (#88, pipeline).
  18. _51DEGREES_CLOUD_ENDPOINT replaces FOD_CLOUD_API_URL, which still works in this release. When no endpoint is set in code or configuration, CloudRequestEngineBuilder and DidClient read _51DEGREES_CLOUD_ENDPOINT, and read FOD_CLOUD_API_URL only when the new name is unset or empty. The first use of the old name in a process is reported as deprecated, as a warning through the builder's logger, and by DidClient through System.Diagnostics.Trace. Constants.FOD_CLOUD_API_URL and DidClient.EndpointEnvironmentVariable still hold FOD_CLOUD_API_URL and compile with an obsolete warning, and Constants.CLOUD_ENDPOINT_ENV_VAR and the new DidClient.CloudEndpointEnvironmentVariable hold the new name. Set _51DEGREES_CLOUD_ENDPOINT to the same value as the old name (#131, #143, pipeline). The examples, tests and CI scripts also read every old name in the table under "Environment variables" as a deprecated name, when its new name is unset or empty (#144).

What changes

Web integration and client-side caching

  • A request whose If-None-Match matches gets 304 for GET and HEAD, and 412 for any other method, as RFC ...
Read more

pipeline/4.5.129

Choose a tag to compare

@Automation51D Automation51D released this 04 Nov 23:13
4d7152b

What's Changed

Full Changelog: https://github.com/51Degrees/51degrees-dotnet/commits/pipeline/4.5.129

location/4.5.196

Choose a tag to compare

@Automation51D Automation51D released this 04 Nov 23:14
4d7152b

What's Changed

Full Changelog: https://github.com/51Degrees/51degrees-dotnet/commits/location/4.5.196

ip-intelligence/4.5.155

Choose a tag to compare

@Automation51D Automation51D released this 04 Nov 23:14
4d7152b

What's Changed

Full Changelog: https://github.com/51Degrees/51degrees-dotnet/commits/ip-intelligence/4.5.155

device-detection/4.5.180

Choose a tag to compare

@Automation51D Automation51D released this 04 Nov 23:13
4d7152b

What's Changed

Full Changelog: https://github.com/51Degrees/51degrees-dotnet/commits/device-detection/4.5.180