Ah, right, once only access based on IP. It might be worth taking another approach here and either adjusting this restriction or just outright disabling it. This will allow you to proceed much faster.
Of course, the problem with that is you won't be testing this code - perhaps this table will grow and grow over time and not be indexed properly? To mitigate this risk you could run a component test further down the stack simulating lots of the relevant calls using different IPs. This test could be at the database level directly or perhaps you could write a simple widget of some sort that makes these calls and then call the widget using JMeter passing in a new 'IP string' each time. ----- http://www.http503.com/ -- View this message in context: http://jmeter.512774.n5.nabble.com/Can-t-put-to-Work-the-property-from-HTTP-Request-Source-IP-address-tp5450654p5451074.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]
