jmeter-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Deepak Shetty <>
Subject Re: How to force the port to be used in an HTTP Sampler?
Date Tue, 20 Nov 2012 20:10:08 GMT
As far as I remember browsers like FF dont actually send the ports if they
are the default in the Host header (even if you type out the port
explicitly in the URL) and thats the only place where the port is actually
sent (but I could be wrong) - so when you say it works if I add port which
browser and can you compare whats being sent in the headers etc using some
browser sniffing tool?

The only other place I remember where the port used to cause problems is
buggy AJAX cross domain behavior in some version of a browser but that
doesnt make a difference to JMeter .


On Tue, Nov 20, 2012 at 9:24 AM, Taoism <> wrote:

> shettyd wrote
> > I'd be very surprised if you need the port in the url - what makes you
> > think that?
> I had said the reason in my original message to the list :) (re-pasting it
> below)...
> "If the port is omitted and just https://domain/blah is used I get an
> Internal error from the server.  Adding the port allows the SSO process to
> continue. (Discovered by manually copying the response redirect and pasting
> into a browser). "
> So, I copied and pasted the response redirect both with and without the 443
> port in the URL.  It only kept going if the 443 was present.
> From my perspective it is odd behaviour from the receiving server to
> require
> the port. I am guessing there is some kind of matching rule that looks for
> it.
> Cheers!
> --
> View this message in context:
> Sent from the JMeter - User mailing list archive at
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message