Opened 6 years ago
Last modified 4 years ago
#1494 infoneeded_new defect
I2P-Bote: allow priority in header
Reported by: | user | Owned by: | |
---|---|---|---|
Priority: | trivial | Milestone: | undecided |
Component: | apps/plugins | Version: | 0.9.18 |
Keywords: | I2P-Bote | Cc: | |
Parent Tickets: | Sensitive: | no |
Description
priority can be a useful flag and it has no anonymity implications.
As headers are encrypted only receiver sees it if set.
And update documentation that priority flag is allowed
Subtickets
Change History (4)
comment:1 Changed 6 years ago by
Status: | new → infoneeded_new |
---|
comment:2 follow-up: 3 Changed 5 years ago by
Status: | infoneeded_new → new |
---|
it didn't work for me for some reason. But as it is there, all that's missing is that documentation mention it too, as otherwise docs are wrong saying when they mention what the only things are that get sent and do not include the X-Priority header.
Then this can be closed.
Thx
comment:3 Changed 5 years ago by
Status: | new → infoneeded_new |
---|
Replying to user:
it didn't work for me for some reason. But as it is there, all that's missing is that documentation mention it too, as otherwise docs are wrong saying when they mention what the only things are that get sent and do not include the X-Priority header.
Can you point to where the docs are wrong? Thanks.
comment:4 Changed 4 years ago by
Migrated to https://github.com/i2p/i2p.i2p-bote/issues - I will close these tickets as things are resolved rather than right now, but please make future comments on GitHub?.
X-Priority
has been in the header whitelist since at least 2010, probably earlier.What exactly is it that you want, or are having problems doing?