[ucb-issues] [Issue 21599] Http header HTTP_USER_AGENT
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=21599 User kso changed the following: What|Old value |New value Assigned to|tkr |kso Status|STARTED |NEW --- Additional comments from k...@openoffice.org Fri Feb 18 14:29:57 + 2011 --- ... taking over. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@ucb.openoffice.org For additional commands, e-mail: issues-h...@ucb.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[ucb-issues] [Issue 21599] Http header HTTP_USER_AGENT
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=21599 User kso changed the following: What|Old value |New value CC|'kso' |'' Status|NEW |RESOLVED Resolution| |FIXED --- Additional comments from k...@openoffice.org Fri Feb 18 14:37:48 + 2011 --- Fixed in CWS kso50. OOo now sends a User-Agent request header with every request. The header value format is ooo-product-name/ooo-product-version neon/neon-version. Examples: OpenOffice.org/3.4 neon/0.29.5, Oracle Open Office/3.4 neon/0.29.5. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@ucb.openoffice.org For additional commands, e-mail: issues-h...@ucb.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[ucb-issues] [Issue 21599] Http header HTTP_USER_AGENT
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=21599 --- Additional comments from gr...@openoffice.org Fri Feb 18 17:22:16 + 2011 --- Excellent. Now doc mgmt and CMS systems can retrieve an HTTP_USER_AGENT string from OOo and act accordingly. Any chance on getting this backported to previous OOo versions? - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@ucb.openoffice.org For additional commands, e-mail: issues-h...@ucb.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[ucb-issues] [Issue 21599] Http header HTTP_USER_AGENT
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=21599 User kso changed the following: What|Old value |New value CC|''|'kso' --- Additional comments from k...@openoffice.org Wed Feb 16 14:38:12 + 2011 --- This bug also prevents OpenOffice from being able to access many webdav servers who filter on the user agent string to determine allowable webdav clients or so they can workaround known issues with certain webdav clients. greno: Do you have an example for such a webdav server? I tested this against a webdav server using OOo Writer v3.1.1 and the user agent string delivered by OOo was blank and the server refused to allow access due to the blank user agent string. The user agent string sent by OOo is not blank, the whole useragent request header is simply not present. Not much of a difference here, but for the records. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@ucb.openoffice.org For additional commands, e-mail: issues-h...@ucb.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[ucb-issues] [Issue 21599] Http header HTTP_USER_AGENT
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=21599 --- Additional comments from gr...@openoffice.org Wed Feb 16 16:06:56 + 2011 --- greno: Do you have an example for such a webdav server? Yes, KnowledgeTree. And you can see why doc mgmt and CMS systems using WebDAV have had to query the HTTP_USER_AGENT string because the WebDAV standard can be interpreted differently in a few instances and as a result client implementations have varied. In order to guarantee correct results it has been necessary for servers to query the HTTP_USER_AGENT string in order to determine which type of client is sending the request. This way they can workaround certain client-specific WebDAV implementations. And when a client does not send a HTTP_USER_AGENT string then that client is refused access. This is why OOo has been prevented from working with the WebDAV servers in some of the doc mgmt and CMS systems. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@ucb.openoffice.org For additional commands, e-mail: issues-h...@ucb.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[ucb-issues] [Issue 21599] Http header HTTP_USER_AGENT
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=21599 --- Additional comments from k...@openoffice.org Wed Feb 16 16:22:12 + 2011 --- greno: Do you have a suggestion for the user agent string OOo should send to achieve best interop results? OOo uses neon as webdav client library. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@ucb.openoffice.org For additional commands, e-mail: issues-h...@ucb.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[ucb-issues] [Issue 21599] Http header HTTP_USER_AGENT
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=21599
--- Additional comments from gr...@openoffice.org Wed Feb 16 16:59:23 +
2011 ---
greno: Do you have a suggestion for the user agent string OOo should send to
achieve best interop results? OOo uses neon as webdav client library.
I think you can probably make up any OOo HTTP_USER_AGENT string you like but it
should include some form of neon in it to indicate the neon client library.
In some webdav servers you see things like this:
$user_agent = strtolower($user_agent);
if (strstr($user_agent, 'neon') !== false) {
... do neon specific stuff ...
$allow = True;
}
-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
-
To unsubscribe, e-mail: issues-unsubscr...@ucb.openoffice.org
For additional commands, e-mail: issues-h...@ucb.openoffice.org
-
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org
[ucb-issues] [Issue 21599] Http header HTTP_USER_AGENT
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=21599 --- Additional comments from gr...@openoffice.org Thu Jan 27 01:32:25 + 2011 --- This bug also prevents OpenOffice from being able to access many webdav servers who filter on the user agent string to determine allowable webdav clients or so they can workaround known issues with certain webdav clients. I tested this against a webdav server using OOo Writer v3.1.1 and the user agent string delivered by OOo was blank and the server refused to allow access due to the blank user agent string. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@ucb.openoffice.org For additional commands, e-mail: issues-h...@ucb.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
