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

(fix): readme updated for #271 origin option for * #289

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

dhananjaysa92
Copy link

Updated readme for - #271
Added String- set origin to '*" for all domains to be allowed. This is UNSAFE and not recommended.

README.md Outdated
- `String` - set `origin` to a specific origin. For example if you set it to `"http://example.com"` only requests from "http://example.com" will be allowed.
- `String` - set `origin` to a specific origin. For example, if you set it to
- `"http://example.com"` only requests from "http://example.com" will be allowed.
- `"*"` for all domains to be allowed. This is UNSAFE and not recommended.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is UNSAFE and not recommended.

Can you elaborate on this, please? If it is unsafe and not recommended, then why would we leave this as a feature at all? I'm interested in learning more if you can point to some resources that explain where this statement comes from.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see anything about it being unsafe in your first link and the second link says both it is fine and not fine and doesn't seem conclusive, as it would depend on a lot of factors. The answer also looks like it is CORS in general and nothing specific to this module. The docs of this module should only be about using this module -- not all the details and information about CORS itself, as there are much better sources. A statement like "This is UNSAFE and not recommended." doesn't make any sense, as if it is that way, it shouldn't even be in the module's API.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sounds good. Let me fix it.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dougwilson - pls review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants