1460907481-07b6b3ed-c6a1-4d02-a1fe-c0ec47590287

1. A hydroxyalkyl starch (HAS) for treatment of head and neck cancer wherein the treatment is characterized in reducing tumor growth rates.
2. A hydroxyalkyl starch (HAS) according to claim 1, wherein the hydroxyalkyl starch has a mean molecular weight Mw between 20 and 1300 kDa.
3. A hydroxyalkyl starch (HAS) according to claim 2, wherein the hydroxyalkyl starch has a mean molecular weight Mw between 100 and 110 kDa.
4. A hydroxyalkyl starch (HAS) according to claim 3 with a mean molecular weight of 105 kDa and a molecular substitution MS of 0.42, preferably 0.42+0.05, most preferably 0.4.
5. A hydroxyalkyl starch (HAS) according to claim 2 wherein the hydroxyalkyl starch has a mean molecular weight of 90 to 110 kDa and a molecular substitution MS between 0.9 and 1.1 and a polydispersity index of 1.3.
6. A hydroxyalkyl starch (HAS) according to claim 1 wherein the hydroxyalkyl starch is hydroxyethyl starch.
7. A hydroxyalkyl starch according to claim 1, wherein the head and neck cancer is a solid tumor.
8. A hydroxyalkyl starch according to claim 1, wherein the tumor is selected from the group consisting of cancer of the lips, oral cavity, pharynx, nasal cavity, middle ear, accessory sinuses, larynx and trachea.
9. A hydroxyalkyl starch according to claim 1, wherein the tumor is selected from the group consisting of larynx cancer and oral cavity cancer.
10. A pharmaceutical composition comprising a hydroxyalkyl starch (HAS) as therapeutically active ingredient according to claim 1.
11. A hydroxyalkyl starch (HAS) according to claim 2 wherein the hydroxyalkyl starch is hydroxyethyl starch.
12. A hydroxyalkyl starch (HAS) according to claim 3 wherein the hydroxyalkyl starch is hydroxyethyl starch.
13. A hydroxyalkyl starch (HAS) according to claim 4 wherein the hydroxyalkyl starch is hydroxyethyl starch.
14. A hydroxyalkyl starch (HAS) according claim 5 wherein the hydroxyalkyl starch is hydroxyethyl starch.
15. A hydroxyalkyl starch according to claim 2, wherein the head and neck cancer is a solid tumor.
16. A hydroxyalkyl starch according to claim 3, wherein the head and neck cancer is a solid tumor.
17. A hydroxyalkyl starch according to claim 4, wherein the head and neck cancer is a solid tumor.
18. A hydroxyalkyl starch according to claim 5, wherein the head and neck cancer is a solid tumor.
19. A hydroxyalkyl starch according to claim 6, wherein the head and neck cancer is a solid tumor.
20. A hydroxyalkyl starch according to claim 2, wherein the tumor is selected from the group consisting of cancer of the lips, oral cavity, pharynx, nasal cavity, middle ear, accessory sinuses, larynx and trachea.

The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.

1. A first apparatus comprising:
means for receiving via a network connection, in a case where a first HTTP GET request for a first URL has been generated by a web browser of a second apparatus, first data from which the first URL can be obtained;
means for receiving, from a web server associated with the first URL, a HTTP response to a HTTP GET request for the first URL;
means for obtaining Javascript in accordance with Javascript in the HTTP response such that in the event that Javascript in the HTTP response makes use of web browser-specific information to generate a URL, the execution of the obtained Javascript uses web browser-specific information relating to the web browser of the second apparatus when generating the URL, and
means for executing the obtained Javascript,
wherein a memory and processor are included in the first apparatus.
2. A first apparatus according to claim 1, further comprising means for receiving via a network connection the web browser-specific information relating to the web browser of the second apparatus.
wherein the web browser-specific information relates to a characteristic of the web browser.
3. A first apparatus according to claim 1, wherein the web browser-specific information comprises web browser window geometry.
4. A first apparatus according to claim 1, further comprising means for generating, in accordance with the first data, a second HTTP GET request for the first URL.
5. A first apparatus according to claim 1, further comprising means for generating Javascript which, when processed by the web browser of the second apparatus, causes the second apparatus to send the web browser-specific information to another apparatus.
6. A first apparatus according to claim 5, wherein the Javascript that causes the second apparatus to send the web browser-specific information to another apparatus comprises Javascript that places the web browser-specific information in a URL of a HTTP GET request.
7. A first apparatus according to claim 5, wherein the Javascript that causes the second apparatus to send the web browser-specific information to another apparatus comprises Javascript that places the web browser-specific information in data of a PUT request.
8. A first apparatus according to claim 5, wherein the Javascript that causes the second apparatus to send the web browser-specific information to another apparatus comprises Javascript that places the web browser-specific information in data of a POST request.
9. A first apparatus according to claim 5, wherein the Javascript that causes the second apparatus to send the web browser-specific information to another apparatus comprises Javascript that places the web browser-specific information in a cookie sent via a HTTP transaction.
10. A first apparatus according to claim 5, wherein the Javascript that causes the second apparatus to send the web browser-specific information to another apparatus comprises (a) Javascript that causes the web browser of the second apparatus to obtain the web browser-specific information from the web browser’s Javascript Document Object Model (DOM) and (b) Javascript that causes the web browser of the second apparatus to send the obtained web browser-specific information for receipt by the first apparatus.
11. A first apparatus according to claim 1, wherein the web browser-specific information includes a window width.
12. A first apparatus according to claim 1, wherein the web browser-specific information includes a window height.
13. A first apparatus according to claim 1, wherein the web browser-specific information includes an available width.
14. A first apparatus according to claim 1, wherein the web browser-specific information includes an available height.
15. A first apparatus according to claim 1, wherein the web browser-specific information includes a color depth.
16. A first apparatus according to claim 1, wherein the web browser-specific information includes a pixel depth.
17. A first apparatus according to claim 1, wherein the web browser-specific information includes a timezone.
18. A first apparatus according to claim 1, wherein the web browser-specific information includes a Java-enabled query result.
19. A first apparatus according to claim 1, wherein the web browser-specific information includes browser history information.
20. A first apparatus according to claim 1, wherein the web browser-specific information includes windows geometry information, and
wherein the second apparatus executes a HTTP GET request for a URL, which URL depends upon the window geometry information, to send the windows geometry information for receipt by the first apparatus.
21. A first apparatus according to claim 1, wherein the web browser-specific information includes a browser identity.
22. A first apparatus according to claim 1, wherein the web browser-specific information includes a browser version.
23. A first apparatus according to claim 1, wherein the web browser-specific information includes browser compatibility information.
24. A first apparatus according to claim 1, wherein the web browser-specific information includes information on installed browser plugins.
25. A first apparatus according to claim 24, wherein the information on installed browser plugins includes information on whether Adobe Flash is an installed browser plugin.
26. A first apparatus according to claim 1, wherein a client proxy inserts Javascript into a HTTP response such that when the web browser of the second apparatus executes the Javascript, the Javascript causes the web browser to generates a HTTP request comprising the web browser specific information, and
wherein the client proxy receives the HTTP request and sends the web browser specific information to the first apparatus.
27. A first apparatus comprising:
means for receiving via a network connection web browser-specific information regarding a characteristic of a web browser of a second apparatus; and
means for executing Javascript that makes use of web browser-specific information, using the received web browser-specific information relating to the web browser of the second apparatus instead of web browser-specific information relating to a web browser of the first apparatus,
wherein a memory is included in the first apparatus.
28-30. (canceled)
31. An apparatus-implemented method comprising:
receiving, by a first apparatus comprising a memory and a processor, via a network connection, in a case where a first HTTP GET request for a URL has been generated by a web browser of a second apparatus, data from which the URL can be obtained;
receiving via a network connection web browser-specific information regarding a characteristic of the web browser of the second apparatus;
receiving, from a web server associated with the URL, a HTTP response to a HTTP GET request for the URL;
obtaining Javascript in accordance with Javascript in the HTTP response to the second HTTP GET request, wherein in the event that the Javascript in the HTTP response includes Javascript that makes use of web browser-specific information, the obtained Javascript when executed uses the received web browser-specific information relating to the web browser of the another apparatus; and
executing the obtained Javascript.
32-36. (canceled)
37. An apparatus-implemented method comprising:
receiving by a first apparatus comprising a processor, via a network connection, of Javascript from a HTTP response;
injecting, by the first apparatus into the Javascript, of code that, when executed by a web browser of a second apparatus, causes window geometry information of the web browser to be sent via a network connection to the first apparatus.
38. A first apparatus comprising:
means for receiving via a network connection, in a case where a first HTTP GET request for a first URL has been generated by a second apparatus, first data from which the first URL can be obtained;
means for receiving, from a web server associated with the first URL, second data from a HTTP response to a HTTP GET request for the first URL;
cookie information receiving means for receiving via a network connection cookie information corresponding to a cookie of a first web browser of the second apparatus, wherein the cookie information is received separately from cookie fields of an HTTP header; and
means for storing the cookie information,
wherein a memory and processor are included in the first apparatus.
39. A first apparatus according to claim 38, wherein in response to the first web browser of the second apparatus generating a HTTP GET request that uses a cookie, a client proxy obtains cookie information in accordance with the cookie and sends the cookie information to said cookie information receiving means.
40. A first apparatus according to claim 39, wherein the client proxy is a program stored in a memory of the second apparatus.
41. A first apparatus according to claim 40, wherein the client proxy is a transparent proxy apparatus separate from the first apparatus and the second apparatus.
42. A first apparatus according to claim 38, wherein in response to a HTTP response sent to the first web browser of the second apparatus including a set cookie request, a client proxy obtains cookie information in accordance with the set cookie request and sends the cookie information to said cookie information receiving means.
43-44. (canceled)
45. A first apparatus according to claim 38, further comprising:
a second web browser configured to generate a second HTTP GET request for a second URL;
means for determining, based on the stored cookie information, if the first web browser were to have generated a request for the second URL, whether such request would use a cookie; and
means for, if said determining means determines that a request for the second URL would use a cookie if it had been generated by the first web browser, attaching a cookie from the stored cookie information to the second HTTP GET request to form a modified second HTTP GET request.
46. A first apparatus according to claim 45, further comprising:
means for receiving, from a web server associated with the second URL, third data from a HTTP response to the modified second HTTP GET request for the second URL; and
means for forming a second HTTP response which includes the third data and the cookie from the stored cookie information,
wherein said second web browser receives the second HTTP response as a response to the second HTTP GET request.
47. A first apparatus according to claim 46, wherein the first web browser also receives the third data.
48. A first apparatus according to claim 45, further comprising:
means for updating cookie information stored in said second web browser in accordance with the cookie from the stored cookie information.
49. A first apparatus according to claim 45, wherein the second HTTP GET request is generated in accordance with the second data.
50. A first apparatus according to claim 45, wherein said cookie information receiving means receives the cookie information from a client proxy, the client proxy either being part of or separate from the second apparatus.
51. A first apparatus comprising:
means for receiving via a network connection, in a case where a first HTTP GET request for a first URL has been generated by a second apparatus, first data from which the first URL can be obtained;
means for receiving, from a web server associated with the first URL, second data from a HTTP response to a HTTP GET request for the first URL;
cookie information receiving means for receiving via a network connection cookie information corresponding to a cookie of a first web browser of the second apparatus, the cookie information being other than cookie information from a HTTP header; and
means for storing the cookie information;
a second web browser adapted to generate a second HTTP GET request for a second URL;
means for determining, based on the stored cookie information, if the first web browser were to have generated a request for the second URL, whether such request would use a cookie; and
means for, if said determining means determines that a request for the second URL would use a cookie if it had been generated by the first web browser, attaching a cookie from the stored cookie information to the second HTTP GET request to form a modified second HTTP GET request;
means for receiving, from a web server associated with the second URL, third data from a HTTP response to the modified second HTTP GET request for the second URL; and
means for updating cookie information stored in said second web browser in accordance with the cookie from the stored cookie information,
wherein a memory and processor are included in the first apparatus,
wherein in response to the first web browser of the second apparatus generating a HTTP GET request that uses a cookie, a client proxy obtains cookie information in accordance with the cookie and sends the cookie information to said cookie information receiving means,
wherein in response to an HTTP response sent to the first web browser of the second apparatus including a set cookie request, a client proxy obtains cookie information in accordance with the set cookie request and sends the cookie information to said cookie information receiving means, and
wherein the first web browser also receives the third data.
52. A first apparatus according to claim 51, wherein said updating means includes means for attaching the cookie from the stored cookie information to a HTTP response to the second HTTP GET request which is received by said second web browser.
53-55. (canceled)