Fix the bug in the application to accept requests without having the port as part of the url. On Nov 20, 2012 7:25 PM, "Taoism" <[email protected]> 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: > http://jmeter.512774.n5.nabble.com/How-to-force-the-port-to-be-used-in-an-HTTP-Sampler-tp5715344p5715364.html > Sent from the JMeter - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
