When you use fetch() inside your custom javascript and have your own host, like http://blogname.writeas.com then the server for the api doesnt send a
'Access-Control-Allow-Origin' : '*'- Header.
Solution: Please configure your webserver https://write.as that he adds this header for all CORS-Request. ALL is neccessary, because some users have own domain-names for their blogs. So * is the correct way.
Could you please fix this the fast way? Not waiting some weeks still the shit is rotten? It makes me sometimes a little bit pissed that write.as needs sometimes weeks to fix little things. Thanks!
Can You please fix this, now? I want to use the API and I cant! It is easy to configure, please, I want to code and get along with my work and I wait and wait and problem still open!
Iam absolute disappointed about you. Nobody with a custom domain name can use the api, because the http-server for write.as is not configured to send the correct cors-header. 30D and this bug is still open. Please fix this, I want to use the api in my blog, that works only when you please just do your work. Iam paying customer and I reported the bug, please fix it, thank a lot.
Yeah I don’t appreciate being talked to like that, and we don’t operate like that. I’m one person serving 500,000 people, and I’m not going to drop everything else on my plate to fix a single low-impact issue like this – especially when you’re berating me.
There are workarounds you can use today, if you search this forum. You’ll need to use those for now. And if you aren’t going to be more respectful going forward, I’m going to ignore you.
Hej matt. I beg you pardon, as I said, its time for holyday, for me, too
Please, say me what webserver-combination LAMP you use, then I will recherche the way to send a CORS-Header for all subdomains and for writeas.com, so you save time and we can use the api when we are using our own domainname.
A fix for this actualli is, that you use a CORS-Proxy. I use:
https://corsproxy.io/?https://write.as/api/....
but that must not be that we use a proxy, we want to talk directly to writeas.com
Sorry but you’re selling a service, he was asking you to fix a simple CORS issue, you haven’t responded in 1 month to him, a paying customer, and THIS is your response?
I think I’ll remove writefreely again.
If this is your attitude towards paying customers, I don’t want to know your attitude towards open source users.
Absolutely unacceptable und unprofessional.
