Howdy! I’m trying to run an API call to create a new topic. Discourse API Docs Using Postman I am sending in the API Key / Username / Content-Type as Headers, and JSON data in the body. I have verified the API Username and Key are correct, but, the API call returns the HTML of our sign in page. I…

[Bild] Ryan_NR: HTTP/1.1 307 Temporary Redirect Proxied-By: Service Gateway Appears that you have a very custom setup with a proxy in the middle. That is not standard Discourse behavior, so it looks like this is caused by your special proxy thing. Maybe there is a special Header you can sen…

Can you please paste the cURL version of the API call you are trying to make?

Sure… curl -X POST 'https://staging-discuss.newrelic.com/posts.json' \ -H 'Api-Username: RyanVeitch' -i \ -H 'Api-Key: My-API-Key' -i \ -H 'Content-Type: application/json' \ -d \ '{ "title": "My fancy title", "raw": "Some random text to fill my topic", "category": 21…

Let me know if you need anything else from my side to help in troubleshooting :smiley:

Cool! Thanks @Falco - I’ll dig in with our dev team :slight_smile:

Hey @Falco - I managed to get through the proxy but I’m now being hit by 403 BAD CSRF Errors. I see this thread seems kinda unfinished… [Bild] Improve BAD CSRF error message when making API calls with content-type application/json dev Can you share with me your actual ru…

I just tested your example curl command locally and it is working fine for me so the syntax is all correct. Is is possible the proxy is stripping some headers? That could be why you are getting the BAD CSRF errors because it can no longer read/access the api credentials.

Thanks @blake Our proxy is fully custom in house built and it’s a front layer to the public. I’m VPN’d into our internal network & I’m not hitting the public URL, I’m hitting the backend (behind proxy) URL, so, the requests shouldn’t be going through the proxy. Our staging discourse instance is v…

Nope, v2.3.10 still has all the header based auth stuff so it shouldn’t behave any different. You are hitting this line: app/controllers/application_controller.rb 632ef306e protect_from_forgery # Default Rails 3.2 lets the request through …

Because this is a staging instance and not local you will have nginx or some other webserver running before it hits discourse. It’s possibly nginx is stripping some headers depending on your config. These may show up in the nginx logs. This is the line where it reads the api credentials out of the …

@blake Thanks! I’ll take this up with our dev team :smiley: Appreciate your help

Anomale API-Ergebnisse

Unterstützung

Ryan_NR (Ryan) 25. Juni 2020 um 09:31 7

Hey @Falco – ich habe den Proxy erfolgreich durchlaufen, bekomme aber jetzt 403 BAD CSRF-Fehler.

Ich sehe, dass dieser Thread irgendwie unvollständig wirkt…

Hast du eine Idee, wie man diese Fehler umgehen kann?

Thema		Antworten	Aufrufe
Can't verify CSRF token authenticity while creating topics Development rest-api	1	1186	4. November 2022
Issue with Api Development	1	906	16. August 2022
Discourse admin login throws 403 ["BAD CSRF"] error Support	5	1720	15. September 2020
'BAD CSRF' while creating a new post Support	2	1886	23. Mai 2020
Improve BAD CSRF error message when making API calls with content-type application/json Development	4	4316	14. September 2020

Anomale API-Ergebnisse

Verwandte Themen