-
-
Notifications
You must be signed in to change notification settings - Fork 176
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
Partially corrected CORS checks on the client side #237
base: main
Are you sure you want to change the base?
Conversation
…ill needs an addition
Also a couchdb version check can be added; if it's lower than 3.2 |
Sorry for my absence! and thank you for making this PR! I did not realise it yet! It would be harmless even if |
Yes, checking the remote version should be the correct way. As your mentioned, we should make an easy-usable fix than an easy fix. Would you mind if I ask you to add that logic as well, please? |
Of course I can and I wanted to add it; before that I wanted to hear your opinion. Next week I'll have the free time to add this check and test it out thoroughly. |
DFGTYHKL; |
DFGHJKL/ |
Hi, like explained here since version 3.2 the
enable_cors
option is under[chttpd]
and not[httpd]
. I only moved theenable_cors
option. Result on my testing rig:The
cors.origins
check still needs an addition, it works just fine when there are no spaces between the origins, on my setup I have them so that's the reason why I have this error; since both are valid in the local.ini configuration both can be accepted?