Net::DRI::Transport::HTTP(3pm)

Overview

This module implements an HTTP/HTTPS transport for establishing connections in Net::DRI

Methods

At creation (see Net::DRI "new_profile") you pass a reference to an hash, with the following available keys:

timeout

time to wait (in seconds) for server reply

https_debug https_version https_cert_file https_key_file https_ca_file https_ca_dir

all key materials for https access, if needed

remote_url

URL to access

client_login client_password

protocol login & password

client_newpassword

(optional) new password if you want to change password on login for registries handling that at connection

protocol_connection

Net::DRI class handling protocol connection details. Specifying it should not be needed, as the registry driver should have correct default values.

protocol_data

(optional) opaque data given to protocol_connection class. For EPP, a key login_service_filter may exist, whose value is a code ref. It will be given an array of services, and should give back a similar array; it can be used to filter out some services from those given by the registry.

verify_response

(optional) a callback (code ref) executed after each exchange with the registry, being called with the following parameters: the transport object, the phase (1 for greeting+login, 2 for all normal operations, 3 for logout), the count (if we retried multiple times to send the same message), the message sent (HTTP::Request object) and the response received (HTTP::Response object). This can be used to verify/diagnose SSL details, see example in file t/704opensrs_xcp_live.t

local_host

(optional) the local address (hostname or IP) you want to use to connect (if you are multihomed)

Support

For now, support questions should be sent to:

<[email protected]>

Please also see the SUPPORT file in the distribution.

Releases

Unchanged in 2 releases since Debian 6.0 (Squeeze).

6.0–7