Skip to content

Office 365 public CDN is giving more and more 406 errors... #3238

@sebastienlevert

Description

@sebastienlevert

Category

  • Question
  • Typo
  • Bug
  • Additional article idea

Expected or Desired Behavior

A SharePoint WebPart should always load from the O365 CDN when using Assets Packaging.

Observed Behavior

It works and then... it stops, without changing anything. We are seeing more and more (and customers are reporting more and more) of issues that WebParts files can't be found in https://publiccdn.sharepointonline.com/*.

We're getting those errors in the UI:

screenshot-20190111030812

And when we can reload to get the network trace, we get something like this (both screenshots are not related, it happened in 2 different sessions):

spfxnetworkerror

Steps to Reproduce

This one is really hard to reproduce and we had a good discussion at Ignite with @patmill about this specific issue. Sometimes it fails, then a reload and it starts working again... Basically, deploying a webpart using Assets Packaging and wait for sometimes and be lucky (or unlucky!).

Metadata

Metadata

Assignees

No one assigned

    Labels

    Needs: Triage 🔍Awaiting categorization and initial review.area:cdnCategory: Office 365 Content Delivery Networkstatus:duplicateDuplicate of another issue. See comments for ref to other issue. Dupes closed to consolidate.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions