chore: refresh generated agent instructions
This commit is contained in:
@@ -238,8 +238,8 @@ When implementation is complete, report in Korean:
|
||||
- Redis and scheduling are opt-in through their `kri.*.enabled` settings and matching runtime dependencies.
|
||||
- HTTP bypass targets are server-configured. Never accept an arbitrary full target URL from a frontend; retain allowed-path checks and do not forward hop-by-hop headers.
|
||||
- The external API client returns response bodies as documented, while bypass responses preserve raw bytes and target `Content-Type`.
|
||||
- `ExternalApiClient` multipart requests generate their own boundary and ignore a caller-supplied `Content-Type`. Multipart boundaries and part headers use US-ASCII, `formField` values use UTF-8, and file bodies preserve the supplied bytes.
|
||||
- ASCII multipart filenames are sent unchanged in `filename`. Non-ASCII filenames use a collision-free ASCII `filename` fallback plus the original name in UTF-8 percent-encoded `filename*`; spaces are encoded as `%20`, not `+`.
|
||||
- `ExternalApiClient` multipart requests generate their own boundary and ignore a caller-supplied `Content-Type`. Multipart headers and `formField` values use UTF-8, while file bodies preserve the supplied bytes.
|
||||
- Multipart filenames, including non-ASCII names, are sent unchanged in the quoted `filename` parameter as raw UTF-8. No ASCII fallback or `filename*` parameter is added; CR/LF rejection and quote/backslash escaping still apply.
|
||||
- `JsonUtil` requires the consumer's explicit `ObjectMapper`; shared date/time helpers define KST as `Asia/Seoul` and also expose UTC semantics.
|
||||
|
||||
### Upgrade and Verification
|
||||
Reference in New Issue
Block a user