Closed Bug 403635 Opened 18 years ago Closed 17 years ago

Update help for the new SSL error pages

Categories

(support.mozilla.org :: Knowledge Base Articles, task, P3)

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: sgautherie, Assigned: jason.barnabe)

References

(Blocks 1 open bug, )

Details

Bug 403219 comment 6: {{ neil@parkwaycc.co.uk 2007-11-13 06:49:37 PST If there isn't a bug on adding help for the new SSL error pages, and removing the help pages for these dialogs, can you file one please?. }} NB: I filed this under FireFox to get 'blocking‑firefox3=?' ... Feel free to change this if inappropriate.
Flags: blocking-firefox3?
That's fine as long as help is added for both firefox and SeaMonkey.
Seamonkey can copy the content, I'm not going to require people to patch both.
Flags: blocking-firefox3? → blocking-firefox3+
Priority: -- → P3
Target Milestone: --- → Firefox 3 M11
Does this bug also cover adding help for SSL errors to SUMO?
What are the new SSL error pages?
https://amazon.com, for example.
This should now be a Firefox Support KB article bug. Correct?
yes, correct
Component: Help Documentation → Knowledge Base Articles
Flags: blocking-firefox3+
Product: Firefox → Sumo
QA Contact: help.documentation → kb-articles
Target Milestone: Firefox 3 beta3 → ---
Version: Trunk → unspecified
Target Milestone: --- → 0.6
Assignee: nobody → jason_barnabe
I've started a document at http://support.mozilla.com/kb/Secure+Connection+Failed . It covers self-signed and host mismatch, which are the two I've encountered so far. What are the others, and are there example sites? Are there others going to happen relatively frequently?
Status: NEW → ASSIGNED
Looks good to me. I would only change some esthetic issues. * I don't think users will be able to identify __(site)__ as the domain name. I would rather use something like (site name) without the bold. * I would also use the grey background to distinguish the error message quotes from their explanations. IOW, use ^error message^ * And generally speaking, I think the wording may be too advanced for regular users.
OK, comments addressed. I'm having a hard time explaining the messages accurately and simply without being uselessly vague. Hopefully this is better.
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Moved to KB at: Tue 11 of March, 2008 13:06 EDT Any further discussion about the article should take place on the staging copy of the article: <http://support.mozilla.com/kb/*Secure+Connection+Failed>.
Status: RESOLVED → VERIFIED
(In reply to comment #11) > Any further discussion about the article should take place on the staging copy > of the article: <http://support.mozilla.com/kb/*Secure+Connection+Failed>. This article is Firefox "specific". Neil, or Ian, it looks like nothing has been done about SeaMonkey yet, isn't it ? How shall we proceed ?
(In reply to comment #12) > (In reply to comment #11) > > Any further discussion about the article should take place on the staging copy > > of the article: <http://support.mozilla.com/kb/*Secure+Connection+Failed>. > > This article is Firefox "specific". > > Neil, or Ian, > it looks like nothing has been done about SeaMonkey yet, isn't it ? > How shall we proceed ? > Please file a bug in "MAS: Help", making it depend on this one.
Blocks: 423229
You need to log in before you can comment on or make changes to this bug.