# 오류: 요청한 URL 또는 리소스를 찾을 수 없음
**URL:** https://meta.discourse.org/t/url/402747
**Category:** Bug
**Tags:** fixed
**Created:** [5월 12, 2026, 5:51오전 UTC](https://meta.discourse.org/t/url/402747 "2026-05-12T05:51:15Z")
**Posts on this page:** 1
**Showing post:** 4
### Author:  [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [5월 12, 2026, 1:29오후 UTC](https://meta.discourse.org/t/url/402747/4 "2026-05-12T13:29:36Z")
로컬에서 재현해 봤는데, 예상보다 약간 까다롭네요. 다만 수정을 진행 중입니다.
>
>
> Editing a post that's a reply produced a "The requested URL or resource could no…t be found" dialog when the post had been viewed via its parent's expanded replies list. The dialog came from a \`PUT /post\_replies/:id\` request that 404s; the URL should be \`PUT /posts/:id\`.
>
> \`loadMoreReplies\` calls \`store.find("post-reply", …)\` then \`store.createRecord("post", reply)\` on each result. The first stamps \`\_\_type = "post-reply"\` (and \`\_\_munge\`, \`\_\_state\`) onto each model. The second re-hydrates the same \`id\` under \`post\` — and the topic stream's canonical post for that \`id\` is already in the store. \`\_hydrate\`'s "update existing" path copies those internal fields onto the canonical record via \`setProperties\`, so a later \`post.save()\` builds its URL from the wrong \`\_\_type\`.
>
> Fix: skip every \`\_\_\`-prefixed key when diffing in \`\_hydrate\`'s update path. Internal store/RestModel metadata stamped at hydration time has no business being carried across types. The \`\_\_\` prefix is the existing convention for "internal", so future additions are protected by the same guard.
>
> https://meta.discourse.org/t/402747
---
_[View the full topic](https://meta.discourse.org/t/url/402747)._