6.0.0-beta1
▾
Tasks
New Task
Search
Photos
Wiki
▾
Tickets
New Ticket
Search
dev.horde.org
Toggle Alerts Log
Help
9/22/25
H
istory
A
ttachments
C
omment
W
atch
Download
Comment on [#2565] Firefox 3 bookmarks extension
*
Your Email Address
*
Spam protection
Enter the letters below:
.__ .__ .. ..___. [__)[ __ ||__| | | [_./\__|| | |
Comment
> OK, I just tested https with both a certificate signed by an > Authority in Firefox (it happens to be a self-signed cert from me, > which I used to sign this testing cert), and with a testing > "localhost" certificate that came with Apache. > > > > The CA-signed one gave no warnings at all and I was able to browse > Trean in the browser and use the TreanMarks menu. The testing cert > gave two warnings: that it was not signed by a trusted authority and > that the hostname didn't match. When I accepted it temporarily > however, both browsing and usnig the TreanMarks menu worked. > > > > I even verified with a packet sniffer that the packets were indeed > SSL. I know the error-handling of my plugin could use some > improvement, so perhaps I'll do that within the next few days and you > can try again. If we can't figure anything more out, perhaps some > exchanging of server URLs and test accounts is in order? > > > > Thanks, > > Joey Hewitt > > > >> Mind you, this horde installation is on an SSL-enabled server, so I > >> use https-URLs. > >> I have not looked at the code, but from previous experiences this can > >> lead to problems with javascript/rpc if the certificate is not > >> accepted and such. > >> Just a wild guess. > >
Attachment
Watch this ticket
N
ew Ticket
M
y Tickets
S
earch
Q
uery Builder
R
eports
Saved Queries
Open Bugs
Bugs waiting for Feedback
Open Bugs in Releases
Open Enhancements
Enhancements waiting for Feedback
Bugs with Patches
Enhancements with Patches
Release Showstoppers
Stalled Tickets
New Tickets
Horde 5 Showstoppers