comment on

Sorry to take so long to reply. I may not be the best person, either, as this is a technique I have never used before. As a result, everything here is "I believe" and may not be reliable. I'd be interested in any corrections.

I think you are right that it is simply the overriding of Dancer's existing code. I was getting data out of Dancer by a far more complicated route, but eventually there were only four lines that I incorporated. The first was the call in the code I am developing that became request->address instead of ${request->env}{REMOTE_ADDR}. The second was the three lines

local *Dancer2::Core::Request::address = sub {
    return '127.0.0.2';
};
[download]

that went into the test file. This resulted in Dancer behaving according to the hard coded IP addresses in the test file instead of the IP address of the machine running the tests. Everything in MY garden is roses, but I offer no warranties regarding yours!

Regards,

John Davies

In reply to Re^2: [Solved] Testing Dancer2 - simulating requests from different IP addresses by davies
in thread [Solved] Testing Dancer2 - simulating requests from different IP addresses by davies

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


There's more than one way to do things
	PerlMonks