what if u told her
i love you
and she said
Try again
the operation couldn’t be completed.
(HTTPError{httpCode=badRequest, category=network, cocoa=0, description=‘’})
i love you
and she said
Try again
the operation couldn’t be completed.
(HTTPError{httpCode=badRequest, category=network, cocoa=0, description=‘’})
November 28, 2023 at 10:28 PM
what if u told her
i love you
and she said
Try again
the operation couldn’t be completed.
(HTTPError{httpCode=badRequest, category=network, cocoa=0, description=‘’})
i love you
and she said
Try again
the operation couldn’t be completed.
(HTTPError{httpCode=badRequest, category=network, cocoa=0, description=‘’})
The API response:
"BadRequest: Query is denylisted in Search Content Control tool."
"BadRequest: Query is denylisted in Search Content Control tool."
September 5, 2024 at 6:27 PM
The API response:
"BadRequest: Query is denylisted in Search Content Control tool."
"BadRequest: Query is denylisted in Search Content Control tool."
what if u told her
i love you
and she said
i love you
and she said
November 28, 2023 at 10:25 PM
what if u told her
i love you
and she said
i love you
and she said
え、Googleちゃんどうしたん？
AppScript開こうと思ったらBadRequestってなんで・・・
AppScript開こうと思ったらBadRequestってなんで・・・
December 23, 2024 at 2:44 PM
え、Googleちゃんどうしたん？
AppScript開こうと思ったらBadRequestってなんで・・・
AppScript開こうと思ったらBadRequestってなんで・・・
If I were writing this, it would probably resemble:
if(result.WasSuccessful) return Ok(result);
return BadRequest("It didn't work");
1. No useless comments
2. Logging moved to a filter/middleware or just removed
3. Consider changing BadRequest to more appropriate response code
if(result.WasSuccessful) return Ok(result);
return BadRequest("It didn't work");
1. No useless comments
2. Logging moved to a filter/middleware or just removed
3. Consider changing BadRequest to more appropriate response code
November 21, 2024 at 9:20 PM
If I were writing this, it would probably resemble:
if(result.WasSuccessful) return Ok(result);
return BadRequest("It didn't work");
1. No useless comments
2. Logging moved to a filter/middleware or just removed
3. Consider changing BadRequest to more appropriate response code
if(result.WasSuccessful) return Ok(result);
return BadRequest("It didn't work");
1. No useless comments
2. Logging moved to a filter/middleware or just removed
3. Consider changing BadRequest to more appropriate response code
New blog post: #Azure Data Factory Pipeline Debugging Fails with #BadRequest – The Sequel sqlkover.com/adf-pipeline...
ADF Pipeline Debugging Fails with BadRequest - The Sequel
A while ago I blogged about a use case where a pipeline fails during debugging with a BadRequest error, even though it validates successfully. If you're wondering, this is the helpful error message th...
sqlkover.com
March 6, 2026 at 10:08 AM
New blog post: #Azure Data Factory Pipeline Debugging Fails with #BadRequest – The Sequel sqlkover.com/adf-pipeline...
New blog post: #Azure Data Factory Pipeline Debugging Fails with BadRequest sqlkover.com/azure-data-f...
Azure Data Factory Pipeline Debugging Fails with BadRequest
I recently had a new pipeline fail. It was actually a copy of an old pipeline where I had made some adjustments into as part of a database migration. When triggered during an execution run, it failed ...
sqlkover.com
April 4, 2025 at 11:22 AM
New blog post: #Azure Data Factory Pipeline Debugging Fails with BadRequest sqlkover.com/azure-data-f...
In this case, I would use
return result.WasSuccessful ? Ok(result) : BadRequest("It didn't work");
return result.WasSuccessful ? Ok(result) : BadRequest("It didn't work");
November 21, 2024 at 9:41 PM
In this case, I would use
return result.WasSuccessful ? Ok(result) : BadRequest("It didn't work");
return result.WasSuccessful ? Ok(result) : BadRequest("It didn't work");
something went wrong, we couldn't sign you in. error code CAA20002. AADSTS900434: national cloud request processing failed: CallNationalCloud: http request failed with errorcode: BadRequest, Content: {"error":"invalid_grand","error_description":" 😔
June 30, 2025 at 10:54 PM
something went wrong, we couldn't sign you in. error code CAA20002. AADSTS900434: national cloud request processing failed: CallNationalCloud: http request failed with errorcode: BadRequest, Content: {"error":"invalid_grand","error_description":" 😔
sim, verdade, confesso que no geral eu lanço um badRequest pra não passar muito tempo pensando nisso rs, mas faz bastante sentido sua explicação
September 5, 2024 at 7:02 PM
sim, verdade, confesso que no geral eu lanço um badRequest pra não passar muito tempo pensando nisso rs, mas faz bastante sentido sua explicação
surely
return result.WasSuccessful? Ok(result):BadRequest("It didn't work");
is all you need. Reads well, is concise, and any debug point goes into Ok() and BadRequest()
return result.WasSuccessful? Ok(result):BadRequest("It didn't work");
is all you need. Reads well, is concise, and any debug point goes into Ok() and BadRequest()
November 21, 2024 at 9:54 PM
surely
return result.WasSuccessful? Ok(result):BadRequest("It didn't work");
is all you need. Reads well, is concise, and any debug point goes into Ok() and BadRequest()
return result.WasSuccessful? Ok(result):BadRequest("It didn't work");
is all you need. Reads well, is concise, and any debug point goes into Ok() and BadRequest()
nothing special to do once set up on any working pds!
once it's alive, we just need to see what happens at
`https://relay1.us-east.bsky.network/xrpc/com.atproto.sync.getRepoStatus?did=<NEW_DID>`
we have bug repro if response `BadRequest failed to proxy` like fordid:plc:r47ixofywwpyonnqd5d4pmaz
once it's alive, we just need to see what happens at
`https://relay1.us-east.bsky.network/xrpc/com.atproto.sync.getRepoStatus?did=<NEW_DID>`
we have bug repro if response `BadRequest failed to proxy` like fordid:plc:r47ixofywwpyonnqd5d4pmaz
relay1.us-east.bsky.network
August 28, 2025 at 8:18 PM
nothing special to do once set up on any working pds!
once it's alive, we just need to see what happens at
`https://relay1.us-east.bsky.network/xrpc/com.atproto.sync.getRepoStatus?did=<NEW_DID>`
we have bug repro if response `BadRequest failed to proxy` like fordid:plc:r47ixofywwpyonnqd5d4pmaz
once it's alive, we just need to see what happens at
`https://relay1.us-east.bsky.network/xrpc/com.atproto.sync.getRepoStatus?did=<NEW_DID>`
we have bug repro if response `BadRequest failed to proxy` like fordid:plc:r47ixofywwpyonnqd5d4pmaz
Hmm
POST request to chaga.us-west.host.bsky.network/xrpc/com.atp... failed with status code BadRequest, "InvalidRequest" "Lexicon not found: lex:app.bsky.graph.verification"
POST request to chaga.us-west.host.bsky.network/xrpc/com.atp... failed with status code BadRequest, "InvalidRequest" "Lexicon not found: lex:app.bsky.graph.verification"
I should create a personal verification record for Jerry
My new Bluesky tool just dropped... the Verifier tool on @cred.blue! Use it to get a more interactive understanding of @bsky.app's new verification system.
✅ Verify friends
ℹ️ Check your verifications
💞 See which mutuals verified you
Note: this does NOT give you a bluecheck!
cred.blue/verifier
✅ Verify friends
ℹ️ Check your verifications
💞 See which mutuals verified you
Note: this does NOT give you a bluecheck!
cred.blue/verifier
April 22, 2025 at 9:53 PM
Hmm
POST request to chaga.us-west.host.bsky.network/xrpc/com.atp... failed with status code BadRequest, "InvalidRequest" "Lexicon not found: lex:app.bsky.graph.verification"
POST request to chaga.us-west.host.bsky.network/xrpc/com.atp... failed with status code BadRequest, "InvalidRequest" "Lexicon not found: lex:app.bsky.graph.verification"
As a C# programmer if I'm not using curly braces then I'll put them on the same line like:
if (userName == null) return BadRequest();
but it'd be even cooler to be able to do:
if (!userName) return BadRequest();
if (userName == null) return BadRequest();
but it'd be even cooler to be able to do:
if (!userName) return BadRequest();
November 21, 2024 at 11:38 PM
As a C# programmer if I'm not using curly braces then I'll put them on the same line like:
if (userName == null) return BadRequest();
but it'd be even cooler to be able to do:
if (!userName) return BadRequest();
if (userName == null) return BadRequest();
but it'd be even cooler to be able to do:
if (!userName) return BadRequest();
#SkyshareUpdate 2.0.0-preview.r08
- Bluesky同様、投稿への反応を変更できるようになりました（画像参照）
- 画像にAltをつける機能/画像一枚ずつを削除する機能をv1から復帰させました。
- 「クロップ調整」を「サムネ調整」に名前を変更しました。また、サムネ調整ダイアログのUIを改善しました。
- 一部環境においてすべての投稿がBadRequestになる問題を修正しました。
- クリエイターモードの実装に向けた準備のため、バックエンドを大幅にリファクタしました。まだ先になりそうですが、お楽しみに。
- Bluesky同様、投稿への反応を変更できるようになりました（画像参照）
- 画像にAltをつける機能/画像一枚ずつを削除する機能をv1から復帰させました。
- 「クロップ調整」を「サムネ調整」に名前を変更しました。また、サムネ調整ダイアログのUIを改善しました。
- 一部環境においてすべての投稿がBadRequestになる問題を修正しました。
- クリエイターモードの実装に向けた準備のため、バックエンドを大幅にリファクタしました。まだ先になりそうですが、お楽しみに。
September 6, 2026 at 5:15 PM
#SkyshareUpdate 2.0.0-preview.r08
- Bluesky同様、投稿への反応を変更できるようになりました（画像参照）
- 画像にAltをつける機能/画像一枚ずつを削除する機能をv1から復帰させました。
- 「クロップ調整」を「サムネ調整」に名前を変更しました。また、サムネ調整ダイアログのUIを改善しました。
- 一部環境においてすべての投稿がBadRequestになる問題を修正しました。
- クリエイターモードの実装に向けた準備のため、バックエンドを大幅にリファクタしました。まだ先になりそうですが、お楽しみに。
- Bluesky同様、投稿への反応を変更できるようになりました（画像参照）
- 画像にAltをつける機能/画像一枚ずつを削除する機能をv1から復帰させました。
- 「クロップ調整」を「サムネ調整」に名前を変更しました。また、サムネ調整ダイアログのUIを改善しました。
- 一部環境においてすべての投稿がBadRequestになる問題を修正しました。
- クリエイターモードの実装に向けた準備のため、バックエンドを大幅にリファクタしました。まだ先になりそうですが、お楽しみに。
catch (Exception ex)
{
// TODO: tratar cada tipo de erro, mas por enquanto deicha torar
return BadRequest("O Spotify não consegue fazer isso no momento");
}
{
// TODO: tratar cada tipo de erro, mas por enquanto deicha torar
return BadRequest("O Spotify não consegue fazer isso no momento");
}
February 25, 2025 at 3:07 PM
catch (Exception ex)
{
// TODO: tratar cada tipo de erro, mas por enquanto deicha torar
return BadRequest("O Spotify não consegue fazer isso no momento");
}
{
// TODO: tratar cada tipo de erro, mas por enquanto deicha torar
return BadRequest("O Spotify não consegue fazer isso no momento");
}
{"error":{"code":"BadRequest","message":"Invalid version.","innerError":{"date":"2025-04-05T02:17:16","request-id":"74035b24-02c7-4cfa-9f4b-246d2aa891f1","client-request-id":"74035b24-02c7-4cfa-9f4b-246d2aa891f1"}}}
April 5, 2025 at 2:18 AM
{"error":{"code":"BadRequest","message":"Invalid version.","innerError":{"date":"2025-04-05T02:17:16","request-id":"74035b24-02c7-4cfa-9f4b-246d2aa891f1","client-request-id":"74035b24-02c7-4cfa-9f4b-246d2aa891f1"}}}
BadRequest is most likely not the correct status code.
Could use pattern matching to be more concise.
In my company I'd say the log is unnecessary since we use request logging from Serilog.
Comments should give away the intent and not what the code is doing.
Could use pattern matching to be more concise.
In my company I'd say the log is unnecessary since we use request logging from Serilog.
Comments should give away the intent and not what the code is doing.
November 21, 2024 at 9:34 PM
BadRequest is most likely not the correct status code.
Could use pattern matching to be more concise.
In my company I'd say the log is unnecessary since we use request logging from Serilog.
Comments should give away the intent and not what the code is doing.
Could use pattern matching to be more concise.
In my company I'd say the log is unnecessary since we use request logging from Serilog.
Comments should give away the intent and not what the code is doing.
🌙 今夜のもう 1 本
「AI相談が突然400 BadRequestループに陥る原因と、3層防御で直した話」(Zenn (Claude topic))
Claude APIの400エラーを3層防御で根本解決した、実践的なデバッグ手順の記録。
気になった方はぜひ。
#Claude #ClaudeCode
https://hiroba.kojihq.com/articles/2328ea1c852dee
「AI相談が突然400 BadRequestループに陥る原因と、3層防御で直した話」(Zenn (Claude topic))
Claude APIの400エラーを3層防御で根本解決した、実践的なデバッグ手順の記録。
気になった方はぜひ。
#Claude #ClaudeCode
https://hiroba.kojihq.com/articles/2328ea1c852dee
AI相談が突然400 BadRequestループに陥る原因と、3層防御で直した話
Claude APIを使用したAI相談機能で特定ユーザーの会話のみ400 BadRequestエラーが発生。APIキー確認・会話データ検証・入力値サニタイズの3層で原因を特定し解決した実例。API利用者向けのデバッグアプローチ参考記事。
hiroba.kojihq.com
August 26, 2026 at 8:50 AM
🌙 今夜のもう 1 本
「AI相談が突然400 BadRequestループに陥る原因と、3層防御で直した話」(Zenn (Claude topic))
Claude APIの400エラーを3層防御で根本解決した、実践的なデバッグ手順の記録。
気になった方はぜひ。
#Claude #ClaudeCode
https://hiroba.kojihq.com/articles/2328ea1c852dee
「AI相談が突然400 BadRequestループに陥る原因と、3層防御で直した話」(Zenn (Claude topic))
Claude APIの400エラーを3層防御で根本解決した、実践的なデバッグ手順の記録。
気になった方はぜひ。
#Claude #ClaudeCode
https://hiroba.kojihq.com/articles/2328ea1c852dee
三井住友カード、Vpassから定期払いチャンスへ遷移したら400 BadRequest踏んだ。
Cookie長すぎて8400文字超えてて、WAFっぽいのに引っかかって落とされたらしい。エラー画面で再ログイン誘導してほしいけど・・・。
運用するときは各システム跨ぐCookieつけすぎに注意。
Cookie長すぎて8400文字超えてて、WAFっぽいのに引っかかって落とされたらしい。エラー画面で再ログイン誘導してほしいけど・・・。
運用するときは各システム跨ぐCookieつけすぎに注意。
February 13, 2024 at 11:25 AM
三井住友カード、Vpassから定期払いチャンスへ遷移したら400 BadRequest踏んだ。
Cookie長すぎて8400文字超えてて、WAFっぽいのに引っかかって落とされたらしい。エラー画面で再ログイン誘導してほしいけど・・・。
運用するときは各システム跨ぐCookieつけすぎに注意。
Cookie長すぎて8400文字超えてて、WAFっぽいのに引っかかって落とされたらしい。エラー画面で再ログイン誘導してほしいけど・・・。
運用するときは各システム跨ぐCookieつけすぎに注意。
👋🏻 G'day Tim. Issue isn't the BadRequest class, it's the baked in error handling for not-2XX Success message 'status codes'.
Check these docs out (and note the version I was looking at).
I think this doesn't apply to .NET 9+ ?
Check these docs out (and note the version I was looking at).
I think this doesn't apply to .NET 9+ ?
May 5, 2025 at 1:10 PM
👋🏻 G'day Tim. Issue isn't the BadRequest class, it's the baked in error handling for not-2XX Success message 'status codes'.
Check these docs out (and note the version I was looking at).
I think this doesn't apply to .NET 9+ ?
Check these docs out (and note the version I was looking at).
I think this doesn't apply to .NET 9+ ?
Reply/Quote with your review of this code snippet (from a #dotnet API action method):
// check if it worked
if(result.WasSuccessful == false)
{
// return bad request
return BadRequest("It didn't work");
}
// log success
_logger.Log("(whatever)");
// return the result
return Ok(result);
// check if it worked
if(result.WasSuccessful == false)
{
// return bad request
return BadRequest("It didn't work");
}
// log success
_logger.Log("(whatever)");
// return the result
return Ok(result);
November 21, 2024 at 8:48 PM
Reply/Quote with your review of this code snippet (from a #dotnet API action method):
// check if it worked
if(result.WasSuccessful == false)
{
// return bad request
return BadRequest("It didn't work");
}
// log success
_logger.Log("(whatever)");
// return the result
return Ok(result);
// check if it worked
if(result.WasSuccessful == false)
{
// return bad request
return BadRequest("It didn't work");
}
// log success
_logger.Log("(whatever)");
// return the result
return Ok(result);
Success property name is unnecessarily verbose.
I never compare booleans to literals but I do have slight sympathy for the readability argument.
Do we know BadRequest is always the correct response on failure? "it didn't work" definitely isn't.
Comments are redundant. Document properly.
I never compare booleans to literals but I do have slight sympathy for the readability argument.
Do we know BadRequest is always the correct response on failure? "it didn't work" definitely isn't.
Comments are redundant. Document properly.
November 21, 2024 at 9:09 PM
Success property name is unnecessarily verbose.
I never compare booleans to literals but I do have slight sympathy for the readability argument.
Do we know BadRequest is always the correct response on failure? "it didn't work" definitely isn't.
Comments are redundant. Document properly.
I never compare booleans to literals but I do have slight sympathy for the readability argument.
Do we know BadRequest is always the correct response on failure? "it didn't work" definitely isn't.
Comments are redundant. Document properly.