a network 10 for establishing a session may include a browser client 12 communicating over a network such as the internet 14 with a web content server 22 . the communication between the client 12 and server 22 may be via a proxy 16 which during normal communications is a completely transparent communication path . in other words , prior to the occurrence of a trigger event , the proxy 16 may do nothing , in one embodiment , other than to merely transfer communications between the client 12 and the server 22 . thus , a session may exist between the client 12 and the server 22 which is substantially unaffected by the proxy device 16 . the proxy device 16 may be a processor - based system in one embodiment of the present invention . thus , the device 16 may include its own processor and may be coupled to a storage device 18 . the storage device 18 may be any of a variety of known storage devices such as a hard disk drive or a flash memory , as two examples . software 20 , for controlling the operation of the proxy device 16 , may be stored in the storage device 18 . the proxy device 16 may include a proxy engine that will be described in more detail hereinafter . the proxy device 16 may be a dedicated use inbound proxy in one embodiment . the proxy device 16 may be coupled to a shadow browser 24 . the shadow browser 24 may be a client processor - based system in one embodiment . the proxy device 16 and shadow browser 24 are on the server side of the client server communication protocol with respect to the network 14 . thus , the proxy device 16 and the shadow browser 24 may communicate through a relatively high bandwidth connection compared to the connection between the internet 14 and the browser client 12 . turning next to fig2 , the client 12 may access an internet web page by requesting the web page as indicated at 1 . thus , the client 12 requests the web page from the server 22 , for example , by making a http request that travels over the internet 14 . this request may pass unaffected through the proxy device 16 to the content web server 22 . a result is returned from the web server 22 to the browser client 12 via the same logical route . in such case , the proxy device 16 has no affect on the web session which proceeds between the client 12 and the server 22 . however when a trigger occurs , the proxy device 16 intercepts the web page in the form of a data stream and maps the client browser address to a virtual proxy address as indicated at 3 . the proxy device 16 also adds the shadow browser client address to a proxy address table for that session &# 39 ; s address . the proxy device 16 may also forward the domain cookie information refresh instruction requests to a listener on the shadow browser client 24 as indicated at 5 . the shadow client browser 24 then sends a refresh request as indicated at 6 . as a result , the shadow client browser 24 and client 12 both display the same web page . optionally , a chat client session may be invoked between the various session participants which include the client 12 , the server 22 and at least one shadow browser 24 . the trigger event to initiate the session sharing may be a request from the user invoked from code on the client 12 . alternatively , the trigger may be the result of an embedded web page function . for example , referring to fig4 , a help icon 65 may be maintained on the web page 60 . when the user clicks on the help icon 65 , a code may be generated which may be intercepted by the proxy device 16 to initiate session sharing . as still another example , the session sharing may be invoked via an automated call from the web content server 22 . as one example , when the number of data entry errors detected by the server 22 exceeds a predetermined limit during a single web session , the proxy device 16 may be automatically triggered . in one embodiment a secure transaction may be implemented , for example using a modified secure socket layer ( ssl ). ssl may be implemented in the proxy device 16 by renegotiating sessions between the proxy device 16 and the server 22 and between the proxy device 16 and the client 12 , with the proxy device 16 translating for device 16 - client 12 and device 16 - server 22 transactions . where the proxy device 16 and server 12 have a trusted connection , translation may not be needed in device 16 - server 22 transactions . in general the proxy device 16 needs a certificate with any server 22 it interacts with . thus , a ssl proxy may be useful in some situations to negotiate sessions where a pre - existing relationship was not already established . referring to fig3 , the proxy software 20 stored on the proxy device 16 storage 18 begins by detecting the occurrence of an event as indicated at diamond 26 in one embodiment of the present invention . when an event is detected , the requested web page is intercepted from the web server 22 . the client address is then mapped to the proxy device 16 as indicated in block 30 . at this point , the server 22 believes it is communicating with the client 12 but instead is actually communicating with the proxy device 16 . the proxy device 16 then communicates or establishes sessions with both the client 12 and one or more shadow browsers 24 . to implement multiple sessions , the shadow browser 24 address is added to a proxy address table as indicated in block 32 . a refresh request is then forwarded to the shadow client as indicated in block 34 . when the client 12 initiates the refresh request , the shadow browser 24 then displays the same web page displayed by the client 12 . as one example , a help session may be initiated . help desk personnel , managing the shadow browser 24 , see the same web page as the user of the client 12 . the help desk personnel may thereby provide more effective assistance to the user . as still another application , one may invite registered shadow browser users into a shared browser session . each member of the session may have the ability to navigate for the group among any desired web pages or by defining a view only status within the address mapping thereby enabling some active and other passive browser participants . a termination status setting may be set as well . as one example , a setting may determine whether the session is automatically terminated when the initiator leaves the session or when the last participating browser leaves the session . by putting the device 16 which initiates the session sharing on the server side of the network 10 , bandwidth may be conserved . this placement avoids encroaching on the more limited bandwidth constraints of the typical browser user when compared to remote control where client is just remoting software . referring to fig4 , the web page 60 may include a variety of information 62 and 64 to be completed by the user . once the shadow browser 24 is sharing the session with the client 12 , a chat session may be initiated . for example , the user may ask a question 68 and the help desk personnel manning the shadow browser 24 may provide an answer , as indicated at 70 , while viewing the same web page that the user is viewing . while the present invention has been described with respect to a limited number of embodiments , those skilled in the art will appreciate numerous modifications and variations therefrom . it is intended that the appended claims cover all such modifications and variations as fall within the true spirit and scope of this present invention .