Are there plans to release a new version soon? Looks like the last release was in June.
Vitaly Pereverzev
@vitvad
There was nothing to release. I had no time to support or enhance extension
@lightswitch05 your PR will review asap
Daniel
@lightswitch05
Hey @vitvad thank you for merging my pull request. This is an on-going problem for my team and I - if you could release the newest version to the chrome store- it would be very helpful
Daniel
@lightswitch05
This bug is still causing me and my team a lot of trouble. @vitvad if you don't have time to manage this extension, would you be open to adding me as a collaborator?
Ephraim Becker
@EphraimB
Is there any way to get around the access-control-allow-origin without this extension?
Vitaly Pereverzev
@vitvad
chrome --disable-web-security
Fidler
Ephraim Becker
@EphraimB
I mean in any web browser through JavaScript
Vitaly Pereverzev
@vitvad
Search plz "CORS mdn"
In two words - you need to set in header allow-origin record
And server had to respond with access-control-allow-origin
Ephraim Becker
@EphraimB
Can I do this using only JavaScript?
Vitaly Pereverzev
@vitvad
Without extention, run flag or any tool that add this header to response you will get CORS error
You can't change response headers on client side before browser handle them
In that case it will be insecure
Ephraim Becker
@EphraimB
So I have to use a server-side programming language like PHP to do this?
Vitaly Pereverzev
@vitvad
You have to ask your back-end developers to add this header.
Ephraim Becker
@EphraimB
I'm a full-time developer
Vitaly Pereverzev
@vitvad
Glad for you
You mean full-stack ?
Ephraim Becker
@EphraimB
I mean a back-end and front-end
Vitaly Pereverzev
@vitvad
So in this case just add to server response headers corresponding rule
Ephraim Becker
@EphraimB
How?
Vitaly Pereverzev
@vitvad
What language do you use on you back-end
Ephraim Becker
@EphraimB
I was going to do PHP but I don't want to install anything and I have to install PHP to use PHP
Hi, all. Could you please help me to fix an issue, I've already posted - vitvad/Access-Control-Allow-Origin#34 . Looks like need to remove original "Access-Control-Allow-Origin" header before adding "Access-Control-Allow-Origin: *"
ipolegbunin
@ipolegbunin
In chrome header names for CORS are case insensitive. So in background.js comparison should be changed to case insensitive like that "if (header.name.toLowerCase() === rule.data.name.toLowerCase()) {"
Daniel
@lightswitch05
@ipolegbunin this issue has already been fixed - all it needs to to be released by @vitvad
Igor Mozharovsky
@seedofjoy
Hello. Please, review vitvad/Access-Control-Allow-Origin#37 It's no need to set settings in onInstalled event, because on each get we have default settings.
loursbourg
@loursbourg
how to use it?
owntYA
@owntYA
Sup guys.
Anybody in here?
Daniel
@lightswitch05
@vitvad You merged my pull request last october (vitvad/Access-Control-Allow-Origin#32) and have not released a new build since then. Can you please release a new build or add me as a collaborator so that I can release a new one? This issue has been causing lots of problems. Thank you
Yaya7
@Yaya7
Hi
anyone here ?
Bxggi3
@Bxggi3
hi there,i need assistance with cors ,im using a C# .netcore 1.1 based api and my views are using angular to retrieve the json data
WinterSoilder
@WinterSoilder
Hi i want the extension's script to be embedded in my angular app... i know i shoud copy paste the code but whic part and how?? please help.. thank u :smile:
Quinten Lootens
@qlootens
If I only want to allow cors for specific urls, do I only have to change te permissions to the certain urls?
yash chauhan
@yashchauhan28
Hi, How can i implement same functionality with Jquey,Ajax requests in FrontEnd only.