#BadRequest
LightNews LightNews
nekono.dev
作成中のサンプル
スレッド投稿の場合、プレビューのページでスレッドを表示できるようにしようとしている
クロスポストを全部リンクに詰め込むって意味で、一貫性があるかなって
skyshare.nekono.dev/entries/did:...
ねこの 's Post
#SkyshareUpdate 2.0.0-preview.r08 - Bluesky同様、投稿への反応を変更できるようになりました（画像参照） - 画像にAltをつける機能/画像一枚ずつを削除する機能をv1から復帰させました。 - 「クロップ調整」を「サムネ調整」に名前を変更しました。また、サムネ調整ダイアログのUIを改善しました。 - 一部環境においてすべての投稿がBadRequestになる...
skyshare.nekono.dev
September 15, 2026 at 2:01 PM
kojihq.com
🌙 今夜のもう 1 本

「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
September 9, 2026 at 12:50 PM
nekono.dev
#SkyshareUpdate 2.0.0-preview.r08

- Bluesky同様、投稿への反応を変更できるようになりました（画像参照）
- 画像にAltをつける機能/画像一枚ずつを削除する機能をv1から復帰させました。
- 「クロップ調整」を「サムネ調整」に名前を変更しました。また、サムネ調整ダイアログのUIを改善しました。
- 一部環境においてすべての投稿がBadRequestになる問題を修正しました。
- クリエイターモードの実装に向けた準備のため、バックエンドを大幅にリファクタしました。まだ先になりそうですが、お楽しみに。
Altがつけれるようになったよ。 v1であった機能の復帰ですが、今回はClaudeを使っているので、v1よりはずっと安定している...はずです。
September 6, 2026 at 5:15 PM
kojihq.com
🌙 今夜のもう 1 本

「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
community.letsencrypt.org.web.brid.gy
Connection refused [BadRequest :: urn:ietf:params:acme:error:connection]
Hi there, We are receiving this error: 2025-04-10 10:49:21.378 -06:00 INF] Submitting challenge for validation: REDACTEDDOMAIN [http://REDACTEDDOMAIN/.well-known/acme-challenge/vGFM4O8sKCqrKlxoPw28Bvrxw6Ks0m4dB8lPED6_Rbc 2025-04-10 10:49:25.766 -06:00 [ERR] [Progress] Validation failed: REDACTEDDOMAIN Response from Certificate Authority: During secondary validation: IP ADDRESS Fetching http://REDACTEDDOMAIN/.well-known/acme-challenge/vGFM4O8sKCqrKlxoPw28Bvrxw6Ks0m4dB8lPED6_Rbc: Connection refused [BadRequest :: urn:ietf:params:acme:error:connection] 2025-04-10 10:49:25.988 -06:00 [ERR] Validation of the required challenges did not complete successfully. Validation failed: REDACTEDDOMAIN Response from Certificate Authority: During secondary validation: IP ADDRESS: Fetching http://REDACTEDDOMAIN/.well-known/acme-challenge/vGFM4O8sKCqrKlxoPw28Bvrxw6Ks0m4dB8lPED6_Rbc: Connection refused [BadRequest :: urn:ietf:params:acme:error:connection] I did make a test.html file in the C:\inetpub\wwwroot.well-known\acme-challenge path and confirmed I could access from https:///REDACTEDDOMAIN/.well-known/acme-challenge/test.html Any ideas would be nice. We are on 6.1.5.0
community.letsencrypt.org
April 10, 2025 at 5:17 PM
{"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
wesben.bsky.social
Anyone else having trouble logging into SSA.gov? I get #badrequest #socialsecurityadministration #ssa
The United States Social Security Administration | SSA
Official website of the U.S. Social Security Administration.
SSA.gov
March 12, 2025 at 7:14 PM
anny-aqui.swifties.social
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
yee.nu
https://github.com/MarshalX/atproto/issues/192
Had to raise an issue as the Bsky API library broke again after Bsky updated something
BadRequestError createdAt must be an valid atproto datetime (both RFC-3339 and ISO-8601) · Issue #1...
I have started to get the following error whenever I try to post anything at all. I have not made any change in the code but both reposts and normal posts will throw the following error: BadRequest...
github.com
December 5, 2023 at 4:54 PM
yee.nu
It apparently broke a client library so I raised an issue github.com/MarshalX/atp...
BadRequestError createdAt must be an valid atproto datetime (both RFC-3339 and ISO-8601) · Issue #1...
I have started to get the following error whenever I try to post anything at all. I have not made any change in the code but both reposts and normal posts will throw the following error: BadRequest...
github.com
December 5, 2023 at 2:21 PM
yee.nu
Raised an issue: github.com/MarshalX/atp...
BadRequestError createdAt must be an valid atproto datetime (both RFC-3339 and ISO-8601) · Issue #1...
I have started to get the following error whenever I try to post anything at all. I have not made any change in the code but both reposts and normal posts will throw the following error: BadRequest...
github.com
December 5, 2023 at 2:06 AM
yee.nu
BadRequest('400 Bad Request\nYour Tweet text is too long. For more information on how Twitter determines text length see https://github.com/twitter/twitter-text .')
GitHub - twitter/twitter-text: Twitter Text Libraries. This code is used at Twitter to tokenize and ...
Twitter Text Libraries. This code is used at Twitter to tokenize and parse text to meet the expectations for what can be used on the platform. - GitHub - twitter/twitter-text: Twitter Text Librarie...
github.com
November 21, 2023 at 2:34 PM
j416dy.bsky.social
三井住友カード、Vpassから定期払いチャンスへ遷移したら400 BadRequest踏んだ。
Cookie長すぎて8400文字超えてて、WAFっぽいのに引っかかって落とされたらしい。エラー画面で再ログイン誘導してほしいけど・・・。
運用するときは各システム跨ぐCookieつけすぎに注意。
February 13, 2024 at 11:25 AM
franckchester.bsky.social
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()
November 21, 2024 at 9:54 PM
slesa.social.saarland.ap.brid.gy
Ich liebe #microsoft! Ich liebe #azure! Ich liebe einfach ALLES an dieser #SchöneNeueWelt!

*rennt schreiend aus dem Haus
This might be due to timeout or something else. Please try again or contact your ‘admin and share your troubleshooting details. Troubleshooting details Error code: BadRequest
October 17, 2025 at 9:32 AM
numb.comfortab.ly
The API response:

"BadRequest: Query is denylisted in Search Content Control tool."
September 5, 2024 at 6:27 PM
world-domination.com.au
It's not a problem with ProblemDetails (per say) but the way the default error handling is defined for not-200-status codes.

If you:
- ✅ AddProblemDetails()
- ✅ UseStatusCodePages()

and then return
- BadRequest() -> app../json + PD result
- BadRequest("blah") -> app../json but not a PD result
May 5, 2025 at 4:00 PM
world-domination.com.au
👋🏻 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+ ?
May 5, 2025 at 1:10 PM
world-domination.com.au
Hi ASP.NET Core Devs. Is this .. correct?

The Out-Of-The-Box ASP.NET application does not have support for 4XX and 5XX response's *which contain a body*
e.g.
- ✅ return BadRequest(); // No Body
- ❌ return BadRequest("name missing");

UseStatusCodePages only works with *no body*.

cc @davidfowl.com
May 5, 2025 at 9:22 AM
mackuba.eu
Good bot
The key check is [cmd/relay/relay/host.go (line 177)] // port numbers not allowed otherwise if u.Port() != "" { return "", false, fmt.Errorf("port number not allowed for non-local names") } That parser is used directly by public and admin requestCrawl in [cmd/relay/handlers.go (line 26)]. So if you call requestCrawl with: {"hostname":"https://whatever.example:3000"} the relay returns 400 BadRequest before trying to connect. The internal reason is exactly port number not allowed for non-local names. If instead you call requestCrawl with just whatever.example, the relay checks https://whatever.example/xrpc/com.atproto.server.describeServer on the default HTTPS port, effectively 443, via [cmd/relay/handlers.go (line 52)](/Users/kuba/Projects/indigo/cmd/relay/handlers.go:52) and [cmd/relay/relay/host_checker.go (line 57)]. If your PDS only answers on :3000, that check fails as HostNotFound. There is a second blocker during ingest too. When a repo event arrives for a new account, the relay resolves the DID, reads PDSEndpoint(), and runs the same ParseHostname on it in [cmd/relay/relay/account.go (line 70)]. A PLC endpoint of https://whatever.example:3000 fails as new account PDS endpoint invalid, so commits are not accepted/broadcast for that account.
June 27, 2026 at 12:43 AM
kojihq.com
🌙 今夜のもう 1 本

「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 15, 2026 at 8:34 AM
kojihq.com
☀️ 今日のひと記事

「AI相談が突然400 BadRequestループに陥る原因と、3層防御で直した話」(Zenn (Claude topic))

あなたはどう使ってますか?

#Claude #ClaudeCode
https://hiroba.kojihq.com/articles/2328ea1c852dee
AI相談が突然400 BadRequestループに陥る原因と、3層防御で直した話
Claude APIを使用したAI相談機能で特定ユーザーの会話のみ400 BadRequestエラーが発生。APIキー確認・会話データ検証・入力値サニタイズの3層で原因を特定し解決した実例。API利用者向けのデバッグアプローチ参考記事。
hiroba.kojihq.com
July 28, 2026 at 11:08 PM
pub.dev.web.brid.gy
v4.4.1 of layrz_sdk
A Flutter SDK for Layrz, providing tools and utilities for integrating Layrz services into your Flutter applications. Changelog excerpt: - Fixed `BroadcastStatus.BAD_REQUEST`(Go and Python) value to `BAD_REQUEST`, matching the platform's actual API response (was incorrectly `BADREQUEST`). - Added validation to `BroadcastResult.status`(Python) that accepts the legacy `BADREQUEST`string and coerces it to `BAD_REQUEST`. - Initial version on Dart implementation
pub.dev
August 13, 2026 at 11:05 PM
mfthygesen.dk
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.
November 21, 2024 at 9:09 PM
koru05ruco.bsky.social
こんばんは！いつもRPやいいねありがとうございます！

スマホでwebサイトを開こうとした時に「BadRequest」と出た場合は、サーバー側か端末側でエラーが起きてしまってい
のだと思われます。
専門知識があるわけではないので確実ではありませんが、同じ様なことが起きた時に私は「webサイトのキャッシュを削除する」や「スマホ端末の再起動」で回復しました。もしくはブラウザを変えてみるなどですかね。(iPhoneでしたらSafariが標準ですからChromeで試すなど）
参考になれば幸いです！
August 5, 2025 at 12:16 PM