- Posts: 28
- Thank you received: 2
Welcome to the LimeSurvey Community Forum
Ask the community, share ideas, and connect with other LimeSurvey users!
JSON-RPC CORS issue since update yesterday
- mapage
- Topic Author
- Offline
- Junior Member
Less
More
3 weeks 1 day ago #260029
by mapage
JSON-RPC CORS issue since update yesterday was created by mapage
Please help us help you and fill where relevant:
Your LimeSurvey version: LimeSurvey Community Edition Version 6.5.2+240402
Own server or LimeSurvey hosting: hosted home (nas)
Survey theme/template: n/a
==================
Sorry for the basic question but I am using JSON-RPC api's to retrieve user token responses.
As subdomain requester is not the same, I had to activate "Définir l’entête Access-Control-Allow-Origin :" = Oui in order to make it works and it was fine, I could got the sessionKey and retrieve the answers based on a token until yesterday, when I did the update to the last version.
In order to solve this, I tried to restart webserver, activate/deactivate the option to Yes/No again and save the setup.
Unfortunately without any results, as I am a generalist but not expert enough to debug all of this without help.
I could not find specific information on the manual, maybe I was searching on the wrong place.
Does something change in JSON-RPC way of working or pages ? Where to find theses specific pages ? I am interested to better understand this as my scope would like to restrict access as explained in the developer.mozilla.org/en-US/docs/Web/HTTP/CORS documentation : Access-Control-Allow-Origin: foo.example .
Thanks a lot in advance.
C.
PS : same request in a local tool works fine (used insomnia)
Your LimeSurvey version: LimeSurvey Community Edition Version 6.5.2+240402
Own server or LimeSurvey hosting: hosted home (nas)
Survey theme/template: n/a
==================
Sorry for the basic question but I am using JSON-RPC api's to retrieve user token responses.
As subdomain requester is not the same, I had to activate "Définir l’entête Access-Control-Allow-Origin :" = Oui in order to make it works and it was fine, I could got the sessionKey and retrieve the answers based on a token until yesterday, when I did the update to the last version.
In order to solve this, I tried to restart webserver, activate/deactivate the option to Yes/No again and save the setup.
Unfortunately without any results, as I am a generalist but not expert enough to debug all of this without help.
I could not find specific information on the manual, maybe I was searching on the wrong place.
Does something change in JSON-RPC way of working or pages ? Where to find theses specific pages ? I am interested to better understand this as my scope would like to restrict access as explained in the developer.mozilla.org/en-US/docs/Web/HTTP/CORS documentation : Access-Control-Allow-Origin: foo.example .
Thanks a lot in advance.
C.
PS : same request in a local tool works fine (used insomnia)
Please Log in to join the conversation.
- mapage
- Topic Author
- Offline
- Junior Member
Less
More
- Posts: 28
- Thank you received: 2
3 weeks 1 day ago - 3 weeks 1 day ago #260033
by mapage
Replied by mapage on topic JSON-RPC CORS issue since update yesterday
Workaround found : reverse back to previous installation (version LimeSurvey Community Edition Version 6.5.1+240320)
Last edit: 3 weeks 1 day ago by mapage.
Please Log in to join the conversation.
- tpartner
- Away
- LimeSurvey Community Team
Less
More
- Posts: 10110
- Thank you received: 3594
3 weeks 1 day ago #260041
by tpartner
Cheers,
Tony Partner
Solutions, code and workarounds presented in these forums are given without any warranty, implied or otherwise.
Replied by tpartner on topic JSON-RPC CORS issue since update yesterday
Please submit a bug report -
bugs.limesurvey.org
Cheers,
Tony Partner
Solutions, code and workarounds presented in these forums are given without any warranty, implied or otherwise.
Please Log in to join the conversation.