| Mark all unread [message #15610] |
Tue, 23 December 2003 14:35  |
Gribnif
Messages: 82
Registered: December 2003
Karma: 0
|
Member |
|
|
Try this sequence:
1. Refresh the home page. Assuming you have some new messages, proceed with #2.
2. Click on the topic with new messages, then a thread to read them.
3. Hit your browser's Back button twice, to return to the Home page without reloading it. It still shows the topic you just read as "unread", which is to be expected.
4. Click on the "Mark all messages read" link.
5. FUD now displays a series of messages, possibly even including the ones you just read.
I would expect the "mark all" option to always just refresh the home page, showing all the topics as completely read. Why does it try to show messages at all? This seems counterintuitive to me.
[Edit: fixed a typo]
[Updated on: Tue, 23 December 2003 14:38] Report message to a moderator |
|
|
|
| Re: Mark all unread [message #15611 is a reply to message #15610] |
Tue, 23 December 2003 16:18  |
Ilia
Messages: 13241
Registered: January 2002
Karma: 0
|
Senior Member
Administrator
Core Developer |
|
|
The only way this could've happened is if your browser ignored the no-cache headers when you clicked back. Consequently the forum thinks that the previous URL was the topic display where you get redirected after clicking on the "mark all read" link.
FUDforum Core Developer
|
|
|
|
|
|
|
|
| Re: Mark all unread [message #15803 is a reply to message #15613] |
Mon, 05 January 2004 15:29 |
Gribnif
Messages: 82
Registered: December 2003
Karma: 0
|
Member |
|
|
| Ilia wrote on Tue, 23 December 2003 12:07 |
Expires 0 may work in Safari but looks like a rather invalid header, According to the documentation I've read the Expires header should contain a valid date string. I would think that some 23 years in the past is more then adequate  .
Changing it to 0 may fix it for Safari, but break things for other browsers. I'd recommend reporting this bug to Safari developers.
I should mention that Konqueror 3.2 (on who's engine Safari is based) does not have this problem.
|
Actually, RFC 1945 says:
| Quote: |
Note: Applications are encouraged to be tolerant of bad or misinformed implementations of the Expires header. A value of zero (0) or an invalid date format should be considered equivalent to an "expires immediately." Although these values are not legitimate for HTTP/1.0, a robust implementation is always desirable.
|
So, while it's technically incorrect to use just "0", a browser is expected to support it, and all I've ever used do.
In Safari's case, it seems that this is all that is supported. Yes, that's a bug, but of course getting a major developer to fix anything this tiny is often impossible.
|
|
|
|
| Re: Mark all unread [message #15807 is a reply to message #15803] |
Mon, 05 January 2004 15:57 |
Ilia
Messages: 13241
Registered: January 2002
Karma: 0
|
Senior Member
Administrator
Core Developer |
|
|
As you've said "these values are not legitimate for HTTP/1.0".
So, browsers that for whatever reason use HTTP/1.0 will receive broken headers. The bug is in KTHML and should be reported to the KDE developers, is it up to them to address this issue.
FUDforum Core Developer
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]