You should be actually using: https://rr-n1-tor.opensrs.net/manage/index
Your URL points to RWI (Reseller Web Interface), and this is different then manage. Methods you're trying to execute don't exist in RWI, not to mention different authentication. Z. Dave Delbridge wrote: > Hi Bill, > > > When you say management site, are you talking about manage.opensrs.net? > > Yes, except that we instead use > https://rr-n1-tor.opensrs.net/resellers/index. Erol confirmed that this is > the recommended URL for agents because the page has no frames. > > I'm now suspecting that server redirects are somehow to blame. All of the > links on that page look like: > > /resellers/index?action=manage_nameservers > /resellers/index?action=modify_contact > /resellers/index?action=whois_rsp_info > etc. > > I sincerely doubt that /resellers/index contains one HUGE script that does all > of this stuff. A server redirect probably routes the request to an > appropriate page for processing. If this is true, then the cookie may not > survive to the second page. There are some known issues (and solutions) but > I'll first need to know whether my assumption here is correct. > > Thank you for your reply. > > Dave > > [EMAIL PROTECTED] wrote: > > > Dave, > > > > When you say management site, are you talking about manage.opensrs.net? > > > > If so, my advice would be to program to the API. > > > > Anyway, the behavior you describe (display of the login page) basically > > means that the opensrs manage script did not receive the cookie it was > > expecting. Unfortunately I can't help much there. > > > > On Fri, 16 Nov 2001, Dave Delbridge wrote: > > > > > Hi all, > > > > > > Erol of OpenSRS Support recommended that I drop this question to the > > > list. We are both stumped. > > > > > > I have been writing agent scripts (rather than use the Perl client) > > > without any trouble. ...until now. Logging in, submitting a domain > > > registration or transfer are no problem, but for some reason, when > > > accessing any sub-page of the management site with an agent, I am > > > re-dealt the login screen. Erol assures me that OpenSRS welcomes agents > > > and is not doing anything sneaky to subvert our efforts. > > > > > > My OpenSRS agents perform two simple tasks: > > > > > > 1.) Login and retrieve session cookie * > > > 2.) Submit cookie and form data to desired OpenSRS web page > > > > > > * On reseller site, the cookie delivered is "RESELLER_LIVE_KEY." On > > > management site, the cookie delivered is "REGISTRANT_LIVE_KEY." > > > > > > This approach has worked flawlessly on the Live and Test Reseller > > > Interface. And, the login appears to work on the Live Management > > > Interface, returning a valid-looking session cookie. It's only upon > > > USING that cookie on a subsequent page that we are returned to the login > > > prompt. > > > > > > We are using ColdFusion to script our agents, though this may be > > > irrelevant. I'm aware of a few issues that can defeat agents or disrupt > > > cookie transmission, like server redirects and Java-based cookies, but > > > neither of these are in place for the other OpenSRS pages, so why would > > > they be used here, on the Management Interface? Can somebody confirm > > > for me if indeed they ARE being used? > > > > > > Has anybody else witnessed this behavior? Got a cure? > > > > > > Any help is greatly appreciated. We've come so far. I would hate to > > > have to install the Perl client code now. > > > > > > Thank you so much. > > > > > > Dave > > > > > > -- > > > > > > David M. Delbridge > > > President & CEO > > > Circa 3000 > > > http://www.circa3k.com > > > 775-832-2445 > > > > > > > > > > > -- > > David M. Delbridge > President & CEO > Circa 3000 > http://www.circa3k.com > 775-832-2445
