MAPPING CONNECTIONS AND PROTOCOL-SPECIFIC RESOURCE IDENTIFIERS
Inventors: Joel M. Soderberg, Edmonds, WA (US); Brian J . Deen, North Bend, WA
(US); Alexander I. Hopmann, Seattle,
WA (US) Assignee: Microsoft Corporation, Redmond, WA (U5) Notice: Subject to any disclaimer, the term of this patent is extended or adjusted under 35 U.S.C. 154(b) by 753 days. Appl. N0.: 09/774,963 Filed: Jan. 31, 2001 Prior Publication Data US 2002/0103857 A1 Aug. 1, 2002 Int. Cl.7 ............................................ .. G06F 15/173 U.S. Cl. ............... .. 709/223; 709/225; 709/227 Field of Search ............................... .. 709/223, 225, 709/227
References Cited U.S. PATENT DOCUMENTS
6,081,900 A * 6/2000 Subramaniam et al. 713/201 6,336,137 B1 * 1/2002 Lee et al. ................. .. 709/219
2002/0103881 A1 * 8/2002 Granade et al. .......... .. 709/218
Eun-Kyeong, Yong-Gu, and Ki-Joon, Integrated Transport Layer Security: End -to End Model betWeen WTLS and TLS, Information NetWorking 2001, Jan. 31-Feb. 2, 2001, pp. 65-71.*
Hung and Zhang, On the Feasibility of the Usage of WAP Devices in Telemedicine, IEEE International Conf., Nov. 9-10, 2000, pp. 28-31.*
Primary Examiner—Zarni Maung Assistant Examiner—Ashok B. Patel (74) Attorney, Agent, or Firm—Workman Nydegger
Methods, systems, and computer program products for mapping connections and protocol specific resource identifiers. A front-end server receives a request for content from a client. The front-end server decrypts the request as needed, adds a protocol information to the request that identifies the communication protocol used betWeen the client and the front-end server, and then forWards the request to a back-end server for processing. When the back-end server processes the request, the requested content may include one or more protocol specific resource identifiers. HoWever, the protocol specific resource identifiers are based on the protocol information included in the request rather than the protocol used betWeen the front-end server and the back-end server. Upon receiving the requested content back from the back-end server, the front-end server encrypts the content as needed and sends the content to the requesting client.
34 Claims, 4 Drawing Sheets
s1s1111 111110111 111; I
I _______________ __ — I
1 111o111g1 *7 1
1 BIOS m 1
|__~_ |
1 111111125 1
1 01111111110 1
1 SYSTEM 11; 1
1 1111101111011 I E
, PR.0GRAM61a1 s1s1e1111us 1 F113, 1 1 U L 1 1 E
1:11
1 —— 7 _ 1
1 111111001s11 1111s1111c_111s11 0111011 s111111 NETWORK 1 l°°M1RE1"ETW°RK 1 ___.___ 0111111 1111111 011111 1011
: 118%" 111111111101 11111111111 111111111101 11111111 151
fig :1 .
_ ___‘i"-_ 1111,1111
' “E121 E
141, 11111011 "91 11111011 € ----» c0111>u1s11 0011101111
, ' _ ~_ _ 141 1111001110 ma 01111111110 111110111011 01111211 1110011111 PROGRAM 1 s1s1111 $1 PROGRA1lSm1 11o0u11sm1 111111 mi I3“ '35”
BACK-END ssnvsns INSECURE uarwonx I Pmvlle uerwoax 23° M ; All I I BACK-END , : ssnvsa 2Na I um — REQUEST 250 rR9N1.ENg Hm REQUEST _i.___._. WITH ATTACHED SERVER HEADER 252 BACK-END 219 ssnvan ENCRYPTIDNI g I lb_.. DENWPUON __________. I IIOIIIIIE To PORT BAQK.EN[) j ;11 86 ssaven 2292 HTTP ROUTER M°°"lE BACK-END Z1; seavsn SSL -----RESPONSE 254 RESPONSE ass
|
