On Tue, Oct 31, 2006 at 07:50:06PM +0100, bbackde at googlemail.com wrote: > Situation: > > A key uploaded with filename must be downloaded using the same filename. > A key uploaded without filename must be downloaded without a filename (?) > > But the people post keys in format CHK at abc/xyz , and they don't know > if the file was uploaded with or without a filename. > > How should an application behave if the user enter a key with > CHK at abc/xyz in the download box??? How can the application determine > if it should request the key WITH or WITHOUT the filename?
It should request the key exactly as the user provided it. In the near future, this will continue to work with keys uploaded without filename which have then had a filename appended to them. In the long run, it will yield a specific error code indicating too many path elements. If the client is trying to be excessively helpful and back-compatible it may delete the last path element and try again after receiving such an error message. Just as if fproxy gets an error indicating too few path elements, it appends a "/", and sends a permanent redirect to the new key (the advantage being that bookmarking then keeps the new key rather than the old one). > > Currently Frost completely fails downloading keys WITH filename, > because it removes the filename from the key. > > Help, please! -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: <https://emu.freenetproject.org/pipermail/tech/attachments/20061031/b22a0638/attachment.pgp>
