Feedback says (CORS) error but submits

[c-suh]

🐛 Describe the bug

On submitting something to the Feedback widget, a message will come up that "There was an error sending your feedback." Opening dev tools shows a CORS error. However, the submission goes through. This has been tested from the ATM site, two SBN PSI sites (https://arcnav.psi.edu/ and https://sbn.psi.edu/pds/) and the PDS gamma site.

Notes:

• brought to our attention by Mike Drum
• this didn't seem to be a problem in March (Feedback does not let submissions through for SBN #17 (comment)), unless it was a problem at that time and unnoticed until now

📜 To Reproduce

Steps to reproduce the behavior:

1. Go to pds.nasa.gov
2. Click on "Need Help?" to open the Feedback modal
3. Fill in with your information, indicate it's for testing, and submit
4. See error

🕵️ Expected behavior

Either the submission should not go through, or the feedback widget should give the "Thank you for making PDS a better site" message.

📚 Version of Software Used

v1.3.0, at least on gamma

🩺 Test Data / Additional context

🏞Screenshots

🖥 System Info

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

---

🦄 Related requirements

⚙️ Engineering Details

[jimmie]

Ticket DSIO-2392 opened.

[c-suh]

Sent email to @viviant100 with updates. This is going in the to-do list for me to do after the swagger-ui related task.

[acyu]

I am unable to replicate this issue in Chrome. My version of Chrome is Version 105.0.5195.127. Perhaps this is a browser related issue? Will try with different browser

[c-suh]

Both Allan and I are not able to replicate this issue (although I encountered it at the time this issue was opened). However, Colleen and a PDS user are still encountering the error message while the feedback submission goes through. Further investigation is again paused while addressing other tasks.

[jordanpadams]

@c-suh we should try to get a better understanding of the specific browser and version they are using.

[jordanpadams]

@c-suh FYI, just submitted feedback fine through the RMS widget.

[jordanpadams]

@c-suh adding this back to the sprint backlog since it has reared its head again

[c-suh]

I am getting reacquainted with the details of this bug. Thus far, this is an issue on the nodes' websites which have the feedback widget installed. I just noticed the ticket linked by Jimmie above, and I think we need to continue that conversation. There's an issue with submitting from the pds-engineering site as well, but it's TBD if it's the same or a different issue.

[c-suh]

Talked with Thomas. Have reopened DSIO-2392 with the SAs with a request.

[c-suh]

Still waiting to hear back from the SAs.

[nutjob4life]

Ticket comment did not reopen it. Have let SAs know directly.

[c-suh]

Talked with a SA who requested I open a new ticket: DSIO-4244.

[c-suh]

SA has provided new information which I must look at.

[tloubrieu-jpl]

For SBN the error is related to the recapcha service not being accessible:
https://voight.psi.edu/recaptcha-v3-verify.php.

The CORS headers have been added to the cloudfront function but this is not working. A ticket DSIO-2392 with the SAs has been reopened to investigate a possible conflict with a response header policy.

[jordanpadams]

Note: Additional weirdness from https://pds.nasa.gov/tools/doi/#/search. When you try to submit feedback, the email says it is coming from pds-gamma.jpl.nasa.gov.

[matthewtiscareno]

The feedback button is still broken on the RMS website.

[tloubrieu-jpl]

Yes, sorry @matthewtiscareno we have been pulled away from that ticket because of other priorities. It is still in my to do list.

[tloubrieu-jpl]

Something needs to be done.

[tloubrieu-jpl]

The CORS errors have been fixed by updating the cloudfront function which did not work as needed before.

All the feedbck widgets deployed (ENG, RMS, SBN) now work expect ATM which have a different error related to the recapcha verification, saying I am a bot.

[tloubrieu-jpl]

A new ticket has been created for the recaptcha error, see #20

[tloubrieu-jpl]

The code is not saved on github but is deployed as a cloud front function add_cors_header.

[gxtchen]

@tloubrieu-jpl I am still seeing the error message.

[tloubrieu-jpl]

Hi @gxtchen , that is correct, I am reproducing that. I need to re-investigate that... Can you open a new ticket with the tag i&t and assign it to me ? Thanks.