Thank you so much, Ketan. I think I was thrown off by the fact that it was only some requests that needed it.
Perhaps it makes sense to have it in the Intro or Auth sections rather than in the examples - since those sections are where I go to look for defaults like content negotiations headers and auth headers etc? At any rate, looks like this was a case of PEBKAC caused by !RTFM. Thanks for helping out! On Thursday, July 21, 2016 at 10:24:36 PM UTC-7, Ketan Padegaonkar wrote: > > Yes, as part of some security measures we require a `Confirm: true` > header. This was done to force an OPTIONS check and force a CORS pre-flight > check. > > The docs over at https://api.go.cd will tell you if other requests you're > using have changed. > > On Fri, Jul 22, 2016 at 10:49 AM Badri Janakiraman < > [email protected] <javascript:>> wrote: > >> Hello >> >> Our team recently upgraded from version 16.01 to 16.06. Have there been >> any API changes that might cause the pipeline schedule api to break in this >> release? When I do the following, I get a 404. >> >> curl -IX POST ' >> https://ci.example.com/go/api/pipelines/:pipeline_name/schedule' -u >> 'user:pass' -H 'Accept: application/vnd.go.cd.v1+json' >> >> >> HTTP/1.1 404 Not Found >> >> Cache-Control: no-cache >> >> Content-Type: application/vnd.go.cd.v1+json; charset=utf-8 >> >> Date: Fri, 22 Jul 2016 00:26:32 GMT >> >> Expires: Thu, 01 Jan 1970 00:00:00 GMT >> >> Server: nginx/1.11.2 >> >> Set-Cookie: JSESSIONID=cookie;Path=/go;Expires=Fri, 05-Aug-2016 00:26:32 >> GMT;Secure >> >> X-Content-Type-Options: nosniff >> >> X-Frame-Options: SAMEORIGIN >> >> X-Request-Id: 25d881d6-4cb9-4c84-ac9f-8778308fe601 >> >> X-Runtime: 0.003000 >> >> X-UA-Compatible: chrome=1 >> >> X-XSS-Protection: 1; mode=block >> >> Content-Length: 61 >> >> Connection: keep-alive >> >> >> The same thing happens with the materials & history API too. However, the >> agent and users APIs are fine. This leads me to believe that it is not a >> problem with authentication - but potentially a bug. Or PEBKAC. >> >> >> Our instance is fronted with nginx. The access log shows the 404, >> however, the go-server.log does not seem to show the request being >> processed. Is there some difference to how we are expected to configure >> nginx? >> >> >> Thank you >> >> - Badri >> >> -- >> You received this message because you are subscribed to the Google Groups >> "go-cd" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
