On the 6th of November 2024 at 20:00 UTC, Fastly began to make changes to our device detection library. Our Engineers had identified that these changes would impact a portion of the client variables used in some customer’s custom VCL code. Additionally, as part of this process we have also begun to deprecate a small portion of less frequently used variables. 

Customers identified to have services impacted by this change, would have received an email notification with additional details.

• Refer to subject line, [Action Required] Changes to Device Detection Library 
  • Identified customers should have received messaging on the 4th of October, the 6th of December, and the 19th of December
• A status post reminder was also shared on the 7th of November, reference link

Deprecated variables and changes to make:

Identify where you use the following client.* variables  in your service's custom VCL.

• client.class.checker
• client.class.filter
• client.class.masquerading
• client.class.spam
• client.platform.manufacturer
• client.display.height
• client.display.width
• client.display.ppi
• client.class.downloader
• client.class.feedreader
• client.platform.ereader
• client.platform.tvplayer 

If you are using any of the above deprecated variables, please remove them, or use Client Hints to fetch that information by no later than the 8th of January 2025.

The continued use of these variables after their deprecation date will result in the return of empty values when accessing the device detection library.

If you require Fastly to coordinate with you while performing the upgrade, please contact Fastly Support at https://support.fastly.com to schedule a time to switch to the new library.

Remaining client.* will continue to work with the caveat that some of the string variables will show values differently than before. Our Client request documentation will be updated with the latest variables once this change is completed.

To offer feedback on our status page, click "Give Feedback" 

We are excited to share that the AI Accelerator is now available to all customers as part of our continuous efforts to leverage and optimize AI across our fleet. We’ve heard your feedback and have added additional configurability and extended the supported Large Language Models (LLM) to include OpenAI, Azure OpenAI, Gemini, and other LLMs with OpenAI-compatible APIs. 

For more information, please read our page for how to speed up responses and data processing for AI applications with Fastly. 

I am a beta user. What do I have to do?

Beta access to the AI Accelerator will remain active and all test code will continue to work through the 15th of January 2025.

To continue using the AI Accelerator post-beta, you can navigate to the AI Accelerator landing page on the web interface in the Fastly Application (Select Tools > AI Accelerator) to purchase the product and ensure access beyond the beta grace period. 

If you do not elect to purchase the AI Accelerator product, your access will be revoked and all existing items written within the beta period will no longer be available after the 16th of January 2025.

Contact Information

Customers with any questions or concerns may engage with our Support team through https://support.fastly.com or by contacting your designated account management team members.

Customer Messaging

On the 6th of November 2024 at 20:00 UTC, Fastly began to make changes to our device detection library. Our Engineers had identified that these changes would impact a portion of the client variables used in some customer’s custom VCL code. Additionally, as part of this process we have also begun to deprecate a small portion of less frequently used variables. 

Customers identified to have services impacted by this change, would have received an email notification with additional details.

• Refer to subject line, [Action Required] Changes to Device Detection Library  

Deprecated variables and changes to make:

Identify where you use the following client.* variables  in your service's custom VCL.

• client.class.checker
• client.class.filter
• client.class.masquerading
• client.class.spam
• client.platform.manufacturer
• client.display.height
• client.display.width
• client.display.ppi
• client.class.downloader
• client.class.feedreader
• client.platform.ereader
• client.platform.tvplayer 

If you are using any of the above deprecated variables, please remove them, or use Client Hints to fetch that information by no later than the 8th of January 2025.

The continued use of these variables after their deprecation date will result in the return of empty values when accessing the device detection library.

If you require Fastly to coordinate with you while performing the upgrade, please contact Fastly Support at https://support.fastly.com to schedule a time to switch to the new library.

Remaining client.* will continue to work with the caveat that some of the string variables will show values differently than before. Our Client request documentation will be updated with the latest variables once this change is completed.

Rust has recently deployed a new version, v1.80.

• Shared on their blog: https://blog.rust-lang.org/2024/07/25/Rust-1.80.0.html 

Our teams are currently in the process of upgrading our Rust SDK to be fully compatible with Rust v1.80. Until completed, we are asking our customers to please remain on v1.79.0 until we’ve released a new version of the SDK.

We expect this release will ship within several business days, this release will be shared via our standard practices on: https://docs.rs/fastly/latest/fastly/ 

We have recently posted a thread on the Fastly Community Forum to ask for your feedback on the `fastly.toml` package manifest format as we look to design a new version that more effectively serves the needs of Compute developers: 

• https://community.fastly.com/t/have-your-say-on-the-future-of-fastly-toml/2785  

We invite you to join the discussion and appreciate your insight on how these decisions should be made.

A significant update from Let’s Encrypt, one of our integrated Certification Authorities (CA), may affect how customers access your website. On June 6th, 2024, Let’s Encrypt end-users on very old devices or software may receive insecure warnings or be blocked from accessing your applications. 

Fastly is improving login experiences across Fastly and Signal Sciences consoles to make it simpler and easier for you to access Fastly products and services using a single set of login credentials. Starting Q1 2024, we'll be implementing a new web interface as part of the upgraded login experience. A summary of the main changes appears below.

• Anticipated start date: 20th of February 2024

What's changing? What do I have to do?

You'll log in to Signal Sciences and Fastly accounts with a single set of credentials. Simplified login will allow you to use a single set of login credentials to access all products and features across Fastly's suite of offerings. If you have both Fastly and Signal Sciences accounts that use the same email address, you'll no longer need your Signal Sciences credentials. We'll also make sure to disable and purge your old credentials so they can't be used by accident.

Account linking will no longer be required. When the simplified login experience goes live, customers with both Fastly and Signal Sciences accounts will no longer need to manually link those accounts. Already have linked accounts? You won't need to do anything and can start using your Fastly credentials immediately.

Password changes and 2FA setup will happen in the Fastly console. Likewise, you'll be able to change passwords and set up two-factor authentication directly in the Fastly console for both Fastly and Signal Sciences accounts. This also means that you'll be able to switch between consoles seamlessly without having to log in again.

New passwords will be required to conform to NIST guidelines. Starting Q1 2024, complexity for new and changed passwords will be required to conform to digital identity guidelines from the National Institute of Standards and Technology (specifically, the NIST800-63B guidelines). 

When choosing new passwords and updating existing ones, Fastly will require your passwords to:

• be at least 8 characters long
• be be no more than 72 characters long
• contain at least one letter and one number

In addition, new and changed passwords cannot solely contain:

• sequences of letters or numbers (e.g., 12345678, abcdefg)
• repeated characters (e.g., 222222, aaaaaa)
• adjacent key placements on a standard keyboard (e.g., QWERTY)

The system will specifically prevent you from choosing passwords that:

• match any of your four previous passwords
• match either your username or you email address
• match commonly used passwords (e.g., password123, changeme)
• use popular dictionary words in passwords of fewer than 16 characters (e.g., batterystaple) 

Existing passwords won't be affected until you choose to update them.

Session timeouts will be standardized and more secure. To help you increase your security posture on the Fastly platform, starting Q1 2024 all users will be logged out after 30 minutes of inactivity. Session timeouts will also have a default maximum of 12 hours for any organization that hasn't set up single sign-on. If your session timeout was previously set to greater than 12 hours, it will be reduced to 12 hours, and any timeout setting less than 12 hours will remain as is. The minimum timeout for sessions will be 30 minutes.

What's next? What else do I need to know?

That's it! We'll send you another email reminder about these changes just before the launch. 

Still have questions? Feel free to contact your account manager for additional details.

Fastly Engineers will be releasing our redesigned Fastly App Homepage on the 1st of November 2023.

We have changed our release date of our redesigned Fastly App Homepage to the 15th of November 2023. 

We have constructed an "opt-in" feature that will allow our customers the ability to apply these homepage changes at their convenience.

On the 14th of November 2023 at 01:00 UTC, Fastly Engineering will remove the ERD (old) ports only in our Amsterdam (AMS) Point of Presence (POP) configuration that previously enabled the Azure Zero Rated Egress program. This is in response to an earlier reported change in Microsoft Azure’s Zero Rated Egress practices.

Our network availability and all other services are unaffected by this maintenance.

Additional Information:

Microsoft Azure made a change that affects Fastly’s program for Azure Zero Rated Egress for the AMS POP only and does not impact any other Fastly POP, requiring customers to make a change on their behalf by the 29th of August 2023, in the Microsoft Azure Portal, to retain zero rated egress between Microsoft Azure and Fastly.

On the 8th of August 2023, Fastly reached out to all customers with potential impact and asked that these customers verify their zero rated egress traffic was set with the proper preferences from their Microsoft Azure Billing tools.

Resources:

• What is routing preference unmetered? -Azure Virtual Network
• Outbound Data Transfer from Azure