We're (so far) planning to run an entire site under SSL and we've run 
into a
problem when paging datagrids.  When a user clicks to move to another 
page
of a multi-paged datagrid, the "leaving secure connection" warning 
dialog
pops up. The user clicks on OK, and the next page of the grid displays 
as it
should, apparently still under SSL.

There is no "loading secure page" popup after the user clicks OK - the
system reports when it says it is leaving SSL but not when it is 
returning
to it.  Subsequent access of other documents (web pages) on the site 
remains
under SSL, so I suspect it's not leaving SSL at all, but there's that 
pesky
popup.

In the IIS log, the following two entries appear each time the grid is 
paged
(date, time, client IP, user domain name and server IP removed):

443 POST /PublicDir/SSL_Dir/pageName.aspx - 200
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.1;+.NET+CLR+1.0.3705)
443 GET /PublicDir/SSL_Dir/ - 403
Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.1;+.NET+CLR+1.0.3705)

Our code when paging the datagrid is the standard plain-vanilla:
dg.CurrentPageIndex =3D e.NewPageIndex : UpdateView()  UpdateView simply
retrieves a dataset from Session or the db and re-binds the datagrid to 
it.

Any ideas - wild theories even - are welcome.

TIA