| |
|
| Classification: |
C++ |
Category: |
Networking |
| Created: |
12/17/2004 |
Modified: |
01/17/2005 |
| Number: |
FAQ-1197 |
| Platform: |
Symbian OS v7.0, Symbian OS v7.0s, Symbian OS v8.0, Symbian OS v8.0a, Symbian OS v8.0b, Symbian OS v8.1a, Symbian OS v8.1b |
|
Question:
My code opens multiple SSL/TLS socket connections. When I connect to an invalid site, it pops up a dialog (as expected). However,
even though I acknowledge the dialog, I still get a warning for all the other sockets. Surely the acknowledgement should be
cached?
Answer:
The certificate acknowledgement information should be, and is, cached. Unfortunately, at the point that you acknowledge the
certificate warning dialog, the other sockets have gone past the point where they check the cache to determine whether the
site can be trusted. Therefore each socket pops up its own certificate warning dialog.
If you are opening multiple sockets to a SSL/TLS site, you need to confirm that the first has connected successully before
connecting the other sockets.
|
| |
|
![[Index]](../../a_stock/btn_index_wt.gif){kind=small}
![[spacer]](../../a_stock/btn_spacer.gif){kind=small}
![[Previous]](../../a_stock/btn_prev_wt.gif){kind=small}
![[Next]](../../a_stock/btn_next_wt.gif){kind=small}
![[Previous]](../../a_stock/btn_prev.gif){kind=small}
![[Top]](../../a_stock/btn_top.gif)
![[Next]](../../a_stock/btn_next.gif){kind=small}