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

change exportable http://canvg to //canvg #226

Merged
merged 2 commits into from
Jan 27, 2016
Merged

change exportable http://canvg to //canvg #226

merged 2 commits into from
Jan 27, 2016

Conversation

senluchen2015
Copy link
Contributor

change to allow secure content on IE

drosen0 added a commit that referenced this pull request Jan 27, 2016
change URL for CanVG in exportable.js to omit the protocol
@drosen0 drosen0 merged commit 4745392 into master Jan 27, 2016
@drosen0 drosen0 deleted the exportable-https branch January 27, 2016 00:51
@wglasshusain
Copy link
Contributor

Does it really make sense to load a javascript libary (canvg) from svn? Normally svn is not used as a cdn. If the subversion hosting goes down, then the app is broken. If there's no CDN then I advise simply including it in the project.

@wglasshusain
Copy link
Contributor

Specifically referring to https://canvg.googlecode.com/svn/trunk/ which is hosted by subversion version control, not directly from a file directory on a web site.

@drosen0
Copy link
Contributor

drosen0 commented Jan 27, 2016

@wglasshusain, I totally agree, and it should be addressed. This PR specifically only removed the 'http:' from the URL to fix an issue when used on secure 'https:' sites.

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

Successfully merging this pull request may close these issues.

3 participants