Timeline for Send request to WordPress REST API
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 22, 2019 at 23:11 | answer | added | Derek Held | timeline score: 2 | |
| May 22, 2019 at 23:05 | comment | added | gdfgdfg |
They are on different domains, but now I am trying this plugin rest-api-oauth1 (which is free) and on the server 1 - NodeJS - Request library with OAuth 1.0a library. I think, it works.
|
|
| May 22, 2019 at 22:38 | comment | added | Derek Held | What alternate authentication method are you using to authenticate your requests? Since you are trying to authenticate from a remote server to WordPress you can't use the native cookie method. | |
| May 22, 2019 at 22:19 | history | edited | butlerblog | CC BY-SA 4.0 |
added 21 characters in body; edited title
|
| May 22, 2019 at 21:13 | answer | added | John Swaringen | timeline score: 1 | |
| May 22, 2019 at 21:09 | comment | added | John Swaringen | No I mean are the servers on the same domain? If they aren't you'll have to use CORS. See Cross Domain REST Call using CORS - blogs.mulesoft.com/dev/anypoint-platform-dev/… | |
| May 22, 2019 at 20:38 | comment | added | gdfgdfg | Nope, this is another server, which send requests when something happen on it (server 1 events) | |
| May 22, 2019 at 20:33 | comment | added | John Swaringen | Are you trying to do this with AJAX? Could be a cross domain issue. Which you would need JSONP to do. | |
| May 22, 2019 at 20:25 | history | asked | gdfgdfg | CC BY-SA 4.0 |