controlling outbound port range for XMLHttpRequest??

32 views
Skip to first unread message

ted.s...@gmail.com

unread,
Oct 10, 2008, 8:54:31 AM10/10/08
to Google Web Toolkit
Is it possible to limit the outbound port range for making
XMLHttpRequets? We are running into issues were the client app is
starting to use some ports that are "reserved" by some other custom
applications. When a request is made to a server on port 80 / 443,
what determines the client side port that is opened for that
communication? Is it controlled by GWT, IE / Firefox, etc, OS?

I am using GWT 1.5 and IE 6 on windows xp if it makes any difference.

Thanks!

Ted

Reinier Zwitserloot

unread,
Oct 10, 2008, 9:41:47 AM10/10/08
to Google Web Toolkit
The browser controls that (obviously).

Your network setup is completely, utterly, -BORKED-, if this is
causing problems. That means any connection made by the browser, for
any reason, could randomly fail. I'm guessing you're misunderstanding
the problem.


On Oct 10, 2:54 pm, "ted.slus...@gmail.com" <ted.slus...@gmail.com>
wrote:

walden

unread,
Oct 10, 2008, 9:58:06 AM10/10/08
to Google Web Toolkit
As far as I know, every OS out there has a primitives, available to
programs through a socket library, which choose the "ephemeral" port
for the client side of the binding when a client opens a TCP
connection, cycling through the high range of numbers designated for
that on each new connection request. It is unlikely that your browser
is getting one of the low reserved numbers for its binding. More
likely is that one of your custom applications has "reserved"
something in the ephemeral range. That can work ok, as long as your
custom application starts early enough to get its port bound before
it's given out for some other purpose.

Walden
> > Ted- Hide quoted text -
>
> - Show quoted text -

ted.s...@gmail.com

unread,
Oct 11, 2008, 1:36:00 PM10/11/08
to Google Web Toolkit
It's quite likely than I am misunderstanding or at least not
completely understanding the problem. Can you be more specific in the
BORKness of my network setup? From Walden's reply it sounds like the
custom application is using ports in the "ephemeral" range. Maybe
it's best to change that application to not use ports in that range?
Is that what you mean by BORKED?

Is BORKED a Swedish aphorism? It reminds me of the Swedish chef from
the muppets.

Thanks!

Ted
Reply all
Reply to author
Forward
0 new messages