asked on

Why would my HTTP Header packets be much larger for my remote users?

Greetings,

I manage a Documentum based java application that appears to be making much larger Cookie data in the HTTP headers for some users. Specifically users overseas that have

Accept-Language: en-us,es;q=0.5

Open in new window

set in IE 6 / Windows. I think there may be an application firewall or client configuration that causes much larger HTTP packets for these users than local LAN users.

Of specific note is the Cookie data in the packets. The en, es users in Puerto Rico seem to have much more data in the Cookie portion of the packet , which is making more packets, and contributing to latency.

Here's the cookie portion for a US Mainland user followed by a user in PR:

US:

Cookie: d6_wdk_pref0=eJxTMTS3TUvMKU61UVQxNLYFkibGtiVFqXkplUC2gTlIxNAUocQMzjSytLUyNLGw1Ckoyk9JTM/MB0kb2iLxDAxtkxOLE1OKDYEcUxPb0GB959S8kqLEHBtFANdJIkg.; JSESSIONID=463757EA5A4B0117BC527B457455AEB8; wdk_sess_cookie_0=eJxTMTGzzSvNydEDETaKKiYWtsUlRamJuTmZeakgvrmtiZmxuam5q6Opo4mTgaGhuZOzqZG5k4mpuYmpqaOrkwVQlYGhbXJicWJKsSFIi6WtjSIAUnIXXA..; appname=prodagio_ap; lockFresh=free; allFreshClient=%%cookieTS__client1##1288713288412%%__dmfFreshClient__client1##stale%%__dmfFreshForm__client1##1288713288411

Open in new window

For a PR user:

Cookie: d6_wdk_pref0=eJyNkU1uwjAQhc+ClCVq7QRIqPCCig0bFnAA5NiTyKr/ajuo6elr0oQ2UNpurJnn8RvPN3iR5zizzjDw3hnuhE9RSf0LhCPnkqACpUWV4gLhZV5WxWqSzDISHGjexhjlZDXBnYeD1wZ8MG5wsbSGoxfvQtedFUZD6VU7ZmSj9NGDBBaE0eQQaGj8VNIS5IPQJyMYPHd/6jV4Y2DPpXug3uheZUYp0GF4qAwXVbuhAcZOt8quUSW4sbZWptFDP2tGJac4vXFbPkp3VF3ZHpoytBYuHvuBUK+4q7yiTEgR2lEvK2n8xroD4yPxdEme8KxYTiNETmth7kD9iX6CMBnuYzafkbUCJxh93EBwRoQo4jxut4G7W/3XskbwfoH8bRU327oPuYfxN7XP2NtabjWPY8YxzhNm5HzO+zkTvLhEmHxRTdKMMEm9F2w1+QBcLSDv; JSESSIONID=3C11293391614CC4605AFCAFAA0FE464; wdk_sess_cookie_0=eJxTMTGzzSvNydEDETaKKiYWtsk5icXFmckgjrmtsbOhoZGlsbGloZmhibOziZmBqaObs6Obo6OBm6uJmQlQlYGhbVF+SlFmsZEBSI+lrY0iAACHFnA.; appname=prodagio_ap; timeoutHandler3C11293391614CC4605AFCAFAA0FE464=1288715029743; lockFresh=free; allFreshClient=%%cookieTS__client2##1288714924368%%__dmfFreshClient__client2##stale%%__dmfFreshForm__client2##1288714924367

Open in new window

ASKER CERTIFIED SOLUTION

giltjr

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

eggm4n

ASKER

This is great feedback. I'm taking this to my dev team today. So far I've confirmed that there was a recent upgrade and some client code may be old, and that d6_wdk_pref0 is indeed a user preference string.

My other question would now be, is this typical of a web application to have all of this cookie data in every HTTP Header GET?

giltjr

Cookies must be returned with every request from the browser. This is how the server identifies each unique browser session. Is not the application that does this, its the browser.

Otherwise the server would not be able to tell the difference from my request and your request.

eggm4n

ASKER

Thanks for the advice!