This is a work around that I ended up having to do: Make sure on your HTTP Request (parsing) that you set path, server to '.*' and protocol to https, this will allow the Defaults to fill in the requests and still look for links through HTTPS. Add the parameters that you want it to look for and set the value also to '.*' (remember without quotes). Also you will need to set the parser before this request and after the first request that loads the page with the links. Hope this helps anyone with HTTPS and link parsing problems.
-----Original Message----- From: Craig Palmer [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 11, 2004 5:04 PM To: JMeter Users List Subject: Re: Link parser with SSL? I have logged a bug for this (28677) so I can confirm it is a problem (I using 2.0.0). I did some analysis and found that it fails to find the links because it looses protocol information and ends up only looking for http links. I havent yet had time to figure out exactly why it looses the protocol information. I cant think of a suitable work around in the mean time except to disable the protocol matching test which would required you to recompile some of the source code. Oh yeah, there was a suggestion to try a different HTTP Sampler which I did put much effort into so maybe you should try this (refer jmeter.properties file). Try this and let us know what happens. Craig. Steve Luong wrote: >Hey guys, > >I'm stuck with the link parser trying to hit a random link on a page that is >generated after a user has logged in. > >Does the link parser have a problem with running over an ssl? > > > >I can set up a simple test and it works fine not going over SSL but when I >try it over ssl I have a problem getting it to return a random link. > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
