Is Cache-Control: no-store, no-cache in header a problem for SEs?

I have a script that generates the following page headers:

HTTP/1.1 200 OK:
  Date: Mon, 09 Jan 2006 05:00:39 GMT
  Server: Apache/1.3.33 (Unix)
  Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  Expires: Thu, 19 Nov 1981 08:52:00 GMT
  Pragma: no-cache
  X-Powered-By: PHP/4.4.1
  Set-Cookie: PHPSESSID=3578f9eb1f14aead1fd78cf644a631b3; path=/
  Connection: close
  Transfer-Encoding: chunked
  Content-Type: text/html

Code (markup):

Obviously, the page will not be cached, but will the spiders still read and index the pages? Is there a problem here that could prevent the content from eventually ending up in the SERPs?

 

This part could be a problem:

Set-Cookie: PHPSESSID=3578f9eb1f14aead1fd78cf644a631b3; path=/

Code (markup):

Google and Dynamic Pages

 

Thanks Minstrel.

I tried a couple of spider simulators and the content came through ok. The page will still load without cookies, too. The session ID is not part of the URL. The URL is .com/?go=string

Part of this script is encoded, so I can't change the header creation.

 

I'm not certain that spider simulators will necessarily pick up things spiders can't or won't follow but if you've tested the site with cookies blocked and the site can be navigated without session IDs you're probably OK.

 

Time will tell. No dynamic pages found using site: at Y, G, or M. But the site is only a week old.