Commit a57c133
committed
ci: require HTTP 200 from the archive canary
The canary checked redirects and final host but never the response status,
and curl ran without --fail. A 401 or 404 reports zero redirects with an
Artifactory url_effective, so both assertions passed on a response that
carried no archive — the same shape of false pass the canary was added to
close, reintroduced one layer down. Raised in review of #2376.
Captures %{http_code} and requires 200 before the redirect and host checks
run. Verified the rejected path directly: status 404, redirects 0, host
edge.urm.nvidia.com now fails instead of passing.
Asserting the code rather than relying on --fail keeps the error message
specific — it names the status, where --fail under set -e would kill the
step with no diagnostic, which is how the newline bug in d77849f
presented.
Signed-off-by: Mark Chmarny <mark@chmarny.com>1 parent d77849f commit a57c133
1 file changed
Lines changed: 10 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
168 | 168 | | |
169 | 169 | | |
170 | 170 | | |
171 | | - | |
| 171 | + | |
172 | 172 | | |
173 | 173 | | |
174 | | - | |
| 174 | + | |
175 | 175 | | |
| 176 | + | |
176 | 177 | | |
177 | 178 | | |
178 | 179 | | |
| 180 | + | |
| 181 | + | |
| 182 | + | |
| 183 | + | |
| 184 | + | |
| 185 | + | |
179 | 186 | | |
180 | 187 | | |
181 | 188 | | |
182 | 189 | | |
183 | 190 | | |
184 | 191 | | |
185 | | - | |
| 192 | + | |
186 | 193 | | |
187 | 194 | | |
188 | 195 | | |
| |||
0 commit comments