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

To create a new GDPR report, the user needs to reload the page #8862

Closed
ScharfViktor opened this issue Apr 19, 2023 · 4 comments · Fixed by #10158
Closed

To create a new GDPR report, the user needs to reload the page #8862

ScharfViktor opened this issue Apr 19, 2023 · 4 comments · Fixed by #10158
Assignees
Labels
Priority:p4-low Low priority Type:Bug Something isn't working

Comments

@ScharfViktor
Copy link
Contributor

Steps

  • generate GDPR export: go to account page -> click by request new export button
  • wait generation GDPR export
  • click by Request new export
  • wait for new export

Actual: new export appear only for reloading page

Expected: after generating a new file .personal_data_export.json
image
download export updates

@JammingBen
Copy link
Contributor

There is active polling every 30 seconds, so the user does not have to reload the page. Ideal solution here would be that the server notifies the client about a finished GDPR export, but that's not possible currently.

@ScharfViktor
Copy link
Contributor Author

There is active polling every 30 seconds, so the user does not have to reload the page. Ideal solution here would be that the server notifies the client about a finished GDPR export, but that's not possible currently.

Yes, we wait 30 sec in the case HTTP/1.1 425 TOO EARLY and send new PROPFIND response

but in my case I get PROPFIND <d:status>HTTP/1.1 200 OK</d:status> after POST https://host.docker.internal:9200/graph/v1.0/users/uuid/exportPersonalData and web does't send new PROPFIND request

Screen.Recording.2023-04-19.at.14.31.53.mov

@JammingBen
Copy link
Contributor

Ahh okay, now I got you! This seems to be server related though. Could you please check d:getlastmodified coming from the server? Because it still holds the old date if I'm seeing correctly.

@ScharfViktor
Copy link
Contributor Author

yes, d:getlastmodified contains old date.

@JammingBen JammingBen added Type:Bug Something isn't working Priority:p4-low Low priority labels Jun 26, 2023
@JammingBen JammingBen moved this to Bugs Prio 3 or less in Web Support Board Jun 26, 2023
@kulmann kulmann moved this from Qualification to Prio 3 or less in Infinite Scale Team Board Oct 27, 2023
@JammingBen JammingBen self-assigned this Dec 13, 2023
@JammingBen JammingBen moved this from Prio 3 or less to In progress in Infinite Scale Team Board Dec 13, 2023
@github-project-automation github-project-automation bot moved this from In progress to Done in Infinite Scale Team Board Dec 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority:p4-low Low priority Type:Bug Something isn't working
Projects
Archived in project
Status: Bugs Prio 3 or less
Development

Successfully merging a pull request may close this issue.

2 participants