relay#59 flagged that the edge proxy keeps a second copy of the size disclosure. Measured on production rather than assumed:
POST /api/flamenet/v1/e2e/messages carries RequestContentSize. Ten sends in the window, ten distinct sizes: 6483, 6486, 6510, 6518, 6943, 6971, 20189, 25867.
It is worse than the issue put it. The envelope is erased the moment the app confirms receipt; the access-log line recording how large it was lives for up to a week. The log outlives the row it describes.
/metadata said nothing about this. That page is a promise, so it now says it, alongside the note that padding on the sending device is what would hide both and has not been done, and that an operator who wants neither can turn the access log off.
Also worth recording: the issue's definition of done says /metadata "does not mention size at all". That is stale. The envelopes-table row has covered it in full for a while, verified on the live page, so only this half was missing.
Tests: 697, 0 failures.
relay#59 flagged that the edge proxy keeps a second copy of the size disclosure. Measured on production rather than assumed:
`POST /api/flamenet/v1/e2e/messages` carries `RequestContentSize`. Ten sends in the window, ten distinct sizes: 6483, 6486, 6510, 6518, 6943, 6971, 20189, 25867.
It is worse than the issue put it. The envelope is erased the moment the app confirms receipt; the access-log line recording how large it was lives for up to a week. **The log outlives the row it describes.**
`/metadata` said nothing about this. That page is a promise, so it now says it, alongside the note that padding on the sending device is what would hide both and has not been done, and that an operator who wants neither can turn the access log off.
Also worth recording: the issue's definition of done says `/metadata` "does not mention size at all". That is stale. The envelopes-table row has covered it in full for a while, verified on the live page, so only this half was missing.
Tests: 697, 0 failures.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
relay#59 flagged that the edge proxy keeps a second copy of the size disclosure. Measured on production rather than assumed:
POST /api/flamenet/v1/e2e/messagescarriesRequestContentSize. Ten sends in the window, ten distinct sizes: 6483, 6486, 6510, 6518, 6943, 6971, 20189, 25867.It is worse than the issue put it. The envelope is erased the moment the app confirms receipt; the access-log line recording how large it was lives for up to a week. The log outlives the row it describes.
/metadatasaid nothing about this. That page is a promise, so it now says it, alongside the note that padding on the sending device is what would hide both and has not been done, and that an operator who wants neither can turn the access log off.Also worth recording: the issue's definition of done says
/metadata"does not mention size at all". That is stale. The envelopes-table row has covered it in full for a while, verified on the live page, so only this half was missing.Tests: 697, 0 failures.
mentioned in commit
7932fa99ee