Title: ApexRest -- No 'Access-Control-Allow-Origin' header is present code 401 · Issue #87 · developerforce/Force.com-JavaScript-REST-Toolkit · GitHub
Open Graph Title: ApexRest -- No 'Access-Control-Allow-Origin' header is present code 401 · Issue #87 · developerforce/Force.com-JavaScript-REST-Toolkit
X Title: ApexRest -- No 'Access-Control-Allow-Origin' header is present code 401 · Issue #87 · developerforce/Force.com-JavaScript-REST-Toolkit
Description: We have multiple orgs using ForceTK to call ApexRest services from VisualForce pages. Everything has been working just fine until last night. Now none of our calls are going through: XMLHttpRequest cannot load https://cs41.salesforce.com...
Open Graph Description: We have multiple orgs using ForceTK to call ApexRest services from VisualForce pages. Everything has been working just fine until last night. Now none of our calls are going through: XMLHttpRequest...
X Description: We have multiple orgs using ForceTK to call ApexRest services from VisualForce pages. Everything has been working just fine until last night. Now none of our calls are going through: XMLHttpRequest...
Opengraph URL: https://github.com/developerforce/Force.com-JavaScript-REST-Toolkit/issues/87
X: @github
Domain: patch-diff.githubusercontent.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"ApexRest -- No 'Access-Control-Allow-Origin' header is present code 401","articleBody":"We have multiple orgs using ForceTK to call ApexRest services from VisualForce pages. Everything has been working just fine until last night. Now none of our calls are going through:\n\nXMLHttpRequest cannot load https://cs41.salesforce.com/services/apexrest/v1/productmarkets/. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://c.cs41.visual.force.com' is therefore not allowed access. The response had HTTP status code 401.\n\nWe've added the CORS records to the org with no difference in outcome. I understand that this is more than likely not a ForceTK issue, but something that has changed on the Salesforce side. I'm wondering if anyone might have suggestions on things I can try to get this to work? \n","author":{"url":"https://github.com/craigisakson","@type":"Person","name":"craigisakson"},"datePublished":"2016-07-06T15:06:52.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":19},"url":"https://github.com/87/Force.com-JavaScript-REST-Toolkit/issues/87"}
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:cb0a47fb-2994-c9a4-3430-38cfbfb00de5 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | E892:1B6BE9:9813EF0:C4AF125:69761963 |
| html-safe-nonce | ec11ab1bdc43c54b27b4495274deb0c397d2627d6750e325279578e437353730 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJFODkyOjFCNkJFOTo5ODEzRUYwOkM0QUYxMjU6Njk3NjE5NjMiLCJ2aXNpdG9yX2lkIjoiNzg3NDYwNDQwNjE4NjMxODE3OSIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 2038953fa43619af00a718a19ddf087c67a60b8f8d18bd2f05dd8e8b895e738d |
| hovercard-subject-tag | issue:164098819 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/developerforce/Force.com-JavaScript-REST-Toolkit/87/issue_layout |
| twitter:image | https://avatars.githubusercontent.com/u/366471?s=400&v=4 |
| twitter:card | summary |
| og:image | https://avatars.githubusercontent.com/u/366471?s=400&v=4 |
| og:image:alt | We have multiple orgs using ForceTK to call ApexRest services from VisualForce pages. Everything has been working just fine until last night. Now none of our calls are going through: XMLHttpRequest... |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | craigisakson |
| hostname | github.com |
| expected-hostname | github.com |
| None | c6814b4cc7afd45cd6e64525d0cff0e76dd802f315a5b0e55a7abda1d1d070d0 |
| turbo-cache-control | no-preview |
| go-import | github.com/developerforce/Force.com-JavaScript-REST-Toolkit git https://github.com/developerforce/Force.com-JavaScript-REST-Toolkit.git |
| octolytics-dimension-user_id | 366471 |
| octolytics-dimension-user_login | developerforce |
| octolytics-dimension-repository_id | 1542897 |
| octolytics-dimension-repository_nwo | developerforce/Force.com-JavaScript-REST-Toolkit |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 1542897 |
| octolytics-dimension-repository_network_root_nwo | developerforce/Force.com-JavaScript-REST-Toolkit |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 4ea235bfed58ef16c8a5642b3ac64b74f10c9f52 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width