assert(hostname) error if SOAPCALL to invalid IP

Description

A user tried to do a soapcall to an invalid ip 10.x.x.426 - which resulted in an assert(hostname) error rather than a more helpful error message.

Conclusion

None

Activity

Show:

Richard Chapman February 26, 2015 at 9:36 AM

Richard Chapman February 25, 2015 at 4:50 PM

Ok, this test:

shows a difference between 5.2 and 5.0.6 that could cause some issues

Richard Chapman February 25, 2015 at 4:33 PM

Hmmm - on further investigation that test case behaves the same in 4.0, 4.2, 5.0 and5.2 - I think we should not be changing it.

The assert error that was fixed happens if an invalid ip is passed. Investigating further.

Richard Chapman February 24, 2015 at 1:54 PM

The ONFAIL is not catching the error - it should. We may also need to pass the same info to any onfail transform as previous versions did (or at least check what previous behaviour was so we can tell if anyone was relying on it).

Richard Chapman February 23, 2015 at 3:42 PM

Can you comment?

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Components

Assignee

Reporter

Priority

Fix versions

Affects versions

Created September 18, 2014 at 2:25 PM
Updated February 27, 2015 at 11:10 AM
Resolved February 27, 2015 at 11:10 AM