HELL NO. Please DO NOT USE your crawler on the live ooo bugzilla instance.
If it so happens that you still need that data for some reason, ask for a Bugzilla database dump from [email protected]. Someone will be able to provide you with a sanitized version that contains the info you require. >________________________________ > From: Zhe Liu <[email protected]> >To: [email protected]; Joe Schaefer <[email protected]> >Sent: Friday, May 4, 2012 1:08 AM >Subject: Re: how to access aoo issue website? > >2012/5/4 Joe Schaefer <[email protected]>: >> I explained the situation to Lifeng Wang >> >> already and removed the ban. Please scale >> back your attachment crawler should you >> ever need to use it again. > >You mean you have added the IP to exceptions and we will use the >crawler without any concern in future? > >> Thanks. >> >> >> >> >>>________________________________ >>> From: Zhe Liu <[email protected]> >>>To: [email protected]; Joe Schaefer <[email protected]> >>>Sent: Friday, May 4, 2012 12:58 AM >>>Subject: Re: how to access aoo issue website? >>> >>>Hi Joe, >>>After investigation, I found our team used a robot to collect the >>>attached documents from bugzilla for testing AOO. That leads our IP >>>to be blocked. >>>IP: 202.108.130.138 >>>Could you tell us what is the detail firewall rule? We can change our >>>the schedule and strategy to avoid the problem. >>>Thanks. >>> >>>2012/5/4 Joe Schaefer <[email protected]>: >>>> From what IP address are you trying to connect? >>>> If you send it to me privately I'll check our >>>> firewall rules- if its not there I'm afraid there's >>>> little else we can do. >>>> >>>> >>>> >>>> >>>>>________________________________ >>>>> From: lifeng wang <[email protected]> >>>>>To: [email protected] >>>>>Sent: Thursday, May 3, 2012 10:20 PM >>>>>Subject: Re: how to access aoo issue website? >>>>> >>>>>fail to ping issues.apache.org (140.211.11.121) >>>>> >>>>>2012/5/4 Rob Weir <[email protected]> >>>>> >>>>>> On Thu, May 3, 2012 at 10:03 PM, lifeng wang <[email protected]> >>>>>> wrote: >>>>>> > Still can't connect to Bugzilla today in Beijing >>>>>> > >>>>>> > 2012/5/3 Rob Weir <[email protected]> >>>>>> >>>>>> Works fine for me right now. >>>>>> >>>>>> Can you ping issues.apache.org (140.211.11.121) ? >>>>>> >>>>>> -Rob >>>>>> >>>>>> > >>>>>> >> On Thu, May 3, 2012 at 7:56 AM, Andrea Pescetti <[email protected]> >>>>>> >> wrote: >>>>>> >> > Rob Weir wrote: >>>>>> >> >> >>>>>> >> >> Are you not able to login to Bugzilla? Did you try resetting your >>>>>> >> >> password? >>>>>> >> > >>>>>> >> > >>>>>> >> > Note that the BugZilla home page now has wrong instructions: >>>>>> >> > -- >>>>>> >> > Please Note: All users with accounts on the legacy OpenOffice.org >>>>>> tracker >>>>>> >> > must reset their passwords to gain access to their old accounts. To >>>>>> reset >>>>>> >> > your password, click on the "Forgot Password" link in the header or >>>>>> >> footer. >>>>>> >> > >>>>>> >> > [so far, instruction still apply] >>>>>> >> > >>>>>> >> > Note: If your user name when the service was hosted at Oracle was >>>>>> >> "myuser", >>>>>> >> > then your login for the migrated Bugzilla instance will be >>>>>> >> > "[email protected]" and e-mail to this address will redirect to >>>>>> the >>>>>> >> > e-mail address associated with your Oracle/OpenOffice.org account >>>>>> >> > pre-migration to the ASF. >>>>>> >> > >>>>>> >> > [this part is outdated: users should just write their full e-mail >>>>>> >> address - >>>>>> >> > the real one, not the @openoffice.org alias; at least other users >>>>>> >> reported >>>>>> >> > that this worked for them; I can't test since I migrated my account >>>>>> >> months >>>>>> >> > ago] >>>>>> >> >>>>>> >> OK. I updated the text: https://issues.apache.org/ooo/ >>>>>> >> >>>>>> >> Is that correct? Is there a clearer way to state this? >>>>>> >> >>>>>> >> -Rob >>>>>> >> >>>>>> >> > -- >>>>>> >> > Regards, >>>>>> >> > Andrea. >>>>>> >> >>>>>> >>>>> >>>>> >>>>> >>> >>> >>> >>>-- >>>Best Regards >> >From [email protected] >>> >>> >>> > > > >-- >Best Regards >From [email protected] > > >
