Conversation:

Notices

1. Adam Moore (LÆMEUR) (laemeur)'s status on Thursday, 11-Feb-2016 06:38:41 EST Adam Moore (LÆMEUR)

   Remote profile options...
   !gnusocial — Playing with the API and Javascript, here. Why can I do cross-origin requests to /api/statuses/show, but requests to api/statusnet/conversation fail due to the Access-Control-Allow-Origin headers not being sent?
   • MMN-o ✅⃠ (mmn)'s status on Thursday, 11-Feb-2016 06:43:16 EST MMN-o ✅⃠

     Remote profile options...

     • Adam Moore (LÆMEUR)
     @laemeur I think we should allow CORS _everywhere_ since the request has _already been made_ anyway when the result is sent back.
     
     Problem is we _have to_ supply a CORS header or the default seems to be "I am the webserver, I will throw this response away".
   • Adam Moore (LÆMEUR) (laemeur)'s status on Thursday, 11-Feb-2016 07:10:35 EST Adam Moore (LÆMEUR)

     Remote profile options...

     • MMN-o ✅⃠
     Indeed. I was just wondering if it was intentional that the headers are not being sent, because it would be great to be able to grab conversation feeds via a script, but that's not possible right now.
     !gnusocial
   • MMN-o ✅⃠ (mmn)'s status on Thursday, 11-Feb-2016 07:14:58 EST MMN-o ✅⃠

     Remote profile options...

     • Adam Moore (LÆMEUR)
     @laemeur At least all the API calls should have that header. I guess a header() call could be added in lib/apiaction.php somewhere, which is extended by all the API pages.