Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Requests to WasUpload.ashx are made after turning of CEIP #1461

Closed
1 of 4 tasks
TBag opened this issue Mar 13, 2018 · 7 comments
Closed
1 of 4 tasks

Requests to WasUpload.ashx are made after turning of CEIP #1461

TBag opened this issue Mar 13, 2018 · 7 comments
Labels
area:other Category: unknown (does not fit any other category) status:tracked Currently tracked with Microsoft’s internal issue tracking system. DO NOT ADD/REMOVE (MSFT managed)

Comments

@TBag
Copy link

TBag commented Mar 13, 2018

Category

  • Question
  • Typo
  • Bug
  • Additional article idea

Expected or Desired Behavior

In a SharePoint 2016 on-premises server, when you turn off CEIP, requests to WasUpload.ashx are not made.

Observed Behavior

In a SharePoint 2016 on-premises server, when you turn off CEIP, requests to WasUpload.ashx are made.

Steps to Reproduce

Turn off CEIP on a SP 2016 on-premises server.
Create a hello world SPFx Web Part.
Deploy it to the SP 2016 on-premises farm.
Add it to a page.
Inspect the network traffic when the page loads and see the requests to WasUpload.ashx.

@VesaJuvonen
Copy link
Contributor

Few clarifications for easily issue tracking and to get things moving.

  • CEIP - Customer Experience Improvement Program

@VesaJuvonen VesaJuvonen added status:tracked Currently tracked with Microsoft’s internal issue tracking system. DO NOT ADD/REMOVE (MSFT managed) area:other Category: unknown (does not fit any other category) labels Mar 13, 2018
@VesaJuvonen
Copy link
Contributor

Hi Todd, disabling CEIP in the server does not mean that the wsaUpload.ashx is not called. It means that this information is not shared with Microsoft from the server. You might still see oob web parts and other elements calling this on the client side, as there's no check for CEIP in them one-by-one.

If you inspect network traffic from the server - you should NOT see any information be sent to Microsoft. If you'd see however any traffic from the SP2016 farm towards Microsoft, then that would be a clear bug and an issue.

Closing this for now, unless there are additional details which missed.

@TBag
Copy link
Author

TBag commented Mar 14, 2018

Roger that, thanks.

@marcelaopimenta
Copy link

marcelaopimenta commented Aug 6, 2018

Hi @VesaJuvonen!

Do you have any news? I Have the same problem as @TBag ...

And, my client wants a justification because it is so...

I know I have no communication with Microsoft servers, but the error in console is bringing me a big problem.

Thank you!

Best Regards

@ohiobobcat
Copy link

This has also become an issue for my client due to the console errors, minor performance issues, etc. Opened a ticket with Microsoft and was told that the product team deems this a non issue. I, as well as my client, disagree wholeheartedly.

@samculver
Copy link

samculver commented Jul 19, 2019

Also an issue for my client on SP 2016; we get console errors which cause issues with performance testing. Seems like a bug with the SPFx framework where these calls can't be disabled. There is a global variable in the master page "g_wsaEnabled = false" that should disable this, but SPFx appears to ignore this. It would be great to get a definitive answer that this is or is not a defect with early version of SharePoint Framework for SP 2016. Also, the only way to get rid of the error is to enable CEIP in System Setting in Central Admin, but we don't want to enable this.

@msft-github-bot
Copy link
Collaborator

Issues that have been closed & had no follow-up activity for at least 7 days are automatically locked. Please refer to our wiki for more details, including how to remediate this action if you feel this was done prematurely or in error: Issue List: Our approach to locked issues

@SharePoint SharePoint locked as resolved and limited conversation to collaborators Jan 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area:other Category: unknown (does not fit any other category) status:tracked Currently tracked with Microsoft’s internal issue tracking system. DO NOT ADD/REMOVE (MSFT managed)
Projects
None yet
Development

No branches or pull requests

6 participants