Issue 86729 - Getting http-error 403 for IZ-pages via java-connections
Summary: Getting http-error 403 for IZ-pages via java-connections
Status: CLOSED FIXED
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Bugzilla (show other issues)
Version: current
Hardware: All All
: P2 Trivial (vote)
Target Milestone: ---
Assignee: Unknown
QA Contact: issues@www
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-05 13:46 UTC by hans_werner67
Modified: 2017-05-20 10:27 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description hans_werner67 2008-03-05 13:46:58 UTC 
We have a problem getting data via java-connections, includes xml-parsing the
OOo issue-exports -> produces 403-errors. This problem breaks our imports. I
can't see any problems using a browser with our without internal proxy. It seems
to be a problem on OOo site, cause getting data via java-connection from
www.cnet.com and other sites: no problem occurs. But getting www.openoffice.org
or our issue-data - we have a general problem!

Some more details:
When we use the Apache http-client library or a browser it works fine, but the
xml-parser doesn't use a http-client!!! So I get the stream for the
xml-issue-export by http-client but getting the DTD produces an error:

"java.io.IOException: Server returned HTTP response code: 403 for URL:
http://www.openoffice.org/issues/issuezilla.dtd
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1170)
at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source) ... "

The problem occurs first time today (2008-03-05) in the morning.
The question is: What changed in http-access on OOo site over night???
Frank
Comment 1 hans_werner67 2008-03-05 13:47:51 UTC 
CCed ST and JJ
Comment 2 stx123 2008-03-05 16:42:24 UTC 
reassigning to support...
Please note that access to issues via XML is essential for our daily work. I'm
inclined to raise the priority to P1...
Comment 3 Unknown 2008-03-05 16:47:04 UTC 
Hi,

Thank you for contacting CollabNet Customer Support! Based on the information
provided to us we will present you with an update as soon as we have adequate data.

Thanks,
Harsha
Support Operations.
Comment 4 Unknown 2008-03-05 19:29:00 UTC 
I have filed an internal ticket to our engineering team and will update you on
the progress as we have adequate information.

Thanks,
Harsha
Support Operations.
Comment 5 hans_werner67 2008-03-06 08:57:53 UTC 
It works again, thank you!
In my eyes we can close the issue.
Frank
Comment 6 Unknown 2008-03-06 15:13:56 UTC 
This particular issue appeared due to an block done via squid for controlling an
issue which appeared on the NB side 

http://www.netbeans.org/issues/show_bug.cgi?id=129258