[htdig] ssl patch for ht://dig
Hi
I'm trying to get this ssl patch to work. I finally installed all the
patch, but now I'm getting an error when compiling.
Server.cc: In method `Server::Server(char *, int, int, StringList * =
0)':
Server.cc:44: passing `const char *' as argument 1 of `String::operator
=(char *)' discards qua
lifiers
make[1]: *** [Server.o] Error 1
make[1]: Leaving directory `/tmp/work/htdig-3.1.5/htdig'
make: *** [all] Error 1
This is a line that was modified by the patch. Here is the excert from
Server.cc
//
// Attempt to get a robots.txt file from the specified server
//
String url;
url = ssl ? "https://" : "http://"; this is where it's
getting an error
url host ':' port "/robots.txt";
Documentdoc(url, 0);
static int local_urls_only =
config.Boolean("local_urls_only");
time_t timeZero = 0;
Document::DocStatus status;
Here's the diff
@@ -40,7 +40,8 @@
//
// Attempt to get a robots.txt file from the specified server
//
-String url = "http://";
+String url;
+url = ssl ? "https://" : "http://";
url host ':' port "/robots.txt";
Document doc(url, 0);
Any ideas??
Thanks in advance
Jeremy
begin:vcard
n:Lyon;Jeremy
tel;pager:303-899-9178
tel;work:303-624-4226
x-mozilla-html:FALSE
org:Qwest;Information Technologies
version:2.1
email;internet:[EMAIL PROTECTED]
title:Associate IT Specialist
adr;quoted-printable:;;1515 Arapahoe=0D=0ATower 1=0D=0AFlr 9;Denver;Colorado;80202;
fn:Jeremy Lyon
end:vcard
To unsubscribe from the htdig mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
List archives: http://www.htdig.org/mail/menu.html
FAQ:http://www.htdig.org/FAQ.html
Re: [htdig] SSL Patch
According to Michael Arndt: When applying SSL.0 or SSL.2 (SSL.1 doesnt apply) to a htdig 3.1.5 fresh from Server, i get Problems when trying to compile on a linux box: ... Server.cc: In method `Server::Server(char *, int, int, StringList * = 0)': Server.cc:44: passing `const char *' as argument 1 of `String::operator =(char *)' discards qualifiers Try replacing lines 43-44 of the patched Server.cc with the following construct to see if it would keep your compiler happy: String url = "http://"; if (ssl) url = "https://"; -- Gilles R. Detillieux E-mail: [EMAIL PROTECTED] Spinal Cord Research Centre WWW:http://www.scrc.umanitoba.ca/~grdetil Dept. Physiology, U. of Manitoba Phone: (204)789-3766 Winnipeg, MB R3E 3J7 (Canada) Fax:(204)789-3930 To unsubscribe from the htdig mailing list, send a message to [EMAIL PROTECTED] You will receive a message to confirm this. List archives: http://www.htdig.org/mail/menu.html FAQ:http://www.htdig.org/FAQ.html
Re: [htdig] ssl patch for ht://dig
Gilles,
Thank you so much. That worked. Now I have a new problem. I am indexing from the
local file system. Now
when I do a search everything works fine except the urls that are returned for the ssl
sites appear like
this.
http://ecom.uswest:443/path
It's storing as a regular http:// instead of https:// and it's cutting off the .com.
Any ideas.
Thanks
Jeremy
Gilles Detillieux wrote:
According to Jeremy Lyon:
I'm trying to get this ssl patch to work. I finally installed all the
patch, but now I'm getting an error when compiling.
Server.cc: In method `Server::Server(char *, int, int, StringList * = 0)':
Server.cc:44: passing `const char *' as argument 1 of `String::operator =(char *)'
discards qualifiers
make[1]: *** [Server.o] Error 1
make[1]: Leaving directory `/tmp/work/htdig-3.1.5/htdig'
make: *** [all] Error 1
This is a line that was modified by the patch. Here is the excert from
Server.cc
//
// Attempt to get a robots.txt file from the specified server
//
String url;
url = ssl ? "https://" : "http://"; this is where it's getting an error
url host ':' port "/robots.txt";
Documentdoc(url, 0);
static int local_urls_only = config.Boolean("local_urls_only");
time_t timeZero = 0;
Document::DocStatus status;
Here's the diff
@@ -40,7 +40,8 @@
//
// Attempt to get a robots.txt file from the specified server
//
-String url = "http://";
+String url;
+url = ssl ? "https://" : "http://";
url host ':' port "/robots.txt";
Document doc(url, 0);
Any ideas??
I'd try the following construct to see if it would keep your compiler happy:
String url = "http://";
if (ssl) url = "https://";
This seems to be a compiler bug to me, as there shouldn't be a difference
in the type of a single string literal or a ternary operator with two
string literals as result. We have had reports before of some C++
compilers choking on ternary operators, though, so we have tried to use
them sparingly.
--
Gilles R. Detillieux E-mail: [EMAIL PROTECTED]
Spinal Cord Research Centre WWW:http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba Phone: (204)789-3766
Winnipeg, MB R3E 3J7 (Canada) Fax:(204)789-3930
begin:vcard
n:Lyon;Jeremy
tel;pager:303-899-9178
tel;work:303-624-4226
x-mozilla-html:FALSE
org:Qwest;Information Technologies
version:2.1
email;internet:[EMAIL PROTECTED]
title:Associate IT Specialist
adr;quoted-printable:;;1515 Arapahoe=0D=0ATower 1=0D=0AFlr 9;Denver;Colorado;80202;
fn:Jeremy Lyon
end:vcard
To unsubscribe from the htdig mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
List archives: http://www.htdig.org/mail/menu.html
FAQ:http://www.htdig.org/FAQ.html
Re: [htdig] ssl patch for ht://dig
According to Jeremy Lyon: Gilles, Thank you so much. That worked. Now I have a new problem. I am indexing from the local file system. Now when I do a search everything works fine except the urls that are returned for the ssl sites appear like this. http://ecom.uswest:443/path It's storing as a regular http:// instead of https:// and it's cutting off the .com. Any ideas. Not a clue, but then I haven't had a good long look at the SSL patch to see what it's doing. You should probably ask the developer of the orginal SSL patch (for 3.1.3, I think), as the current one is supposedly a straight port of it to 3.1.5. -- Gilles R. Detillieux E-mail: [EMAIL PROTECTED] Spinal Cord Research Centre WWW:http://www.scrc.umanitoba.ca/~grdetil Dept. Physiology, U. of Manitoba Phone: (204)789-3766 Winnipeg, MB R3E 3J7 (Canada) Fax:(204)789-3930 To unsubscribe from the htdig mailing list, send a message to [EMAIL PROTECTED] You will receive a message to confirm this. List archives: http://www.htdig.org/mail/menu.html FAQ:http://www.htdig.org/FAQ.html
Re: [htdig] ssl patch for ht://dig
According to Jeremy Lyon:
I'm trying to get this ssl patch to work. I finally installed all the
patch, but now I'm getting an error when compiling.
Server.cc: In method `Server::Server(char *, int, int, StringList * = 0)':
Server.cc:44: passing `const char *' as argument 1 of `String::operator =(char *)'
discards qualifiers
make[1]: *** [Server.o] Error 1
make[1]: Leaving directory `/tmp/work/htdig-3.1.5/htdig'
make: *** [all] Error 1
This is a line that was modified by the patch. Here is the excert from
Server.cc
//
// Attempt to get a robots.txt file from the specified server
//
String url;
url = ssl ? "https://" : "http://"; this is where it's getting an error
url host ':' port "/robots.txt";
Documentdoc(url, 0);
static int local_urls_only = config.Boolean("local_urls_only");
time_t timeZero = 0;
Document::DocStatus status;
Here's the diff
@@ -40,7 +40,8 @@
//
// Attempt to get a robots.txt file from the specified server
//
-String url = "http://";
+String url;
+url = ssl ? "https://" : "http://";
url host ':' port "/robots.txt";
Document doc(url, 0);
Any ideas??
I'd try the following construct to see if it would keep your compiler happy:
String url = "http://";
if (ssl) url = "https://";
This seems to be a compiler bug to me, as there shouldn't be a difference
in the type of a single string literal or a ternary operator with two
string literals as result. We have had reports before of some C++
compilers choking on ternary operators, though, so we have tried to use
them sparingly.
--
Gilles R. Detillieux E-mail: [EMAIL PROTECTED]
Spinal Cord Research Centre WWW:http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba Phone: (204)789-3766
Winnipeg, MB R3E 3J7 (Canada) Fax:(204)789-3930
To unsubscribe from the htdig mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
List archives: http://www.htdig.org/mail/menu.html
FAQ:http://www.htdig.org/FAQ.html
[htdig] SSL Patch
When applying SSL.0 or SSL.2 (SSL.1 doesnt apply) to a htdig 3.1.5 fresh from Server, i get Problems when trying to compile on a linux box: thanks for tips Micha ranlib libfuzzy.a make[1]: Leaving directory `/usr1/htdig/htdig-3.1.5/htfuzzy' make[1]: Entering directory `/usr1/htdig/htdig-3.1.5/htdig' c++ -c -DDEFAULT_CONFIG_FILE=\"/opt/www/htdig/conf/htdig.conf\" -I../htlib -I../htcommon -I../db/dist -I../include -I/opt/ssl/include -g -O2 Document.cc c++ -c -DDEFAULT_CONFIG_FILE=\"/opt/www/htdig/conf/htdig.conf\" -I../htlib -I../htcommon -I../db/dist -I../include -I/opt/ssl/include -g -O2 HTML.cc c++ -c -DDEFAULT_CONFIG_FILE=\"/opt/www/htdig/conf/htdig.conf\" -I../htlib -I../htcommon -I../db/dist -I../include -I/opt/ssl/include -g -O2 Images.cc c++ -c -DDEFAULT_CONFIG_FILE=\"/opt/www/htdig/conf/htdig.conf\" -I../htlib -I../htcommon -I../db/dist -I../include -I/opt/ssl/include -g -O2 Parsable.cc c++ -c -DDEFAULT_CONFIG_FILE=\"/opt/www/htdig/conf/htdig.conf\" -I../htlib -I../htcommon -I../db/dist -I../include -I/opt/ssl/include -g -O2 Plaintext.cc c++ -c -DDEFAULT_CONFIG_FILE=\"/opt/www/htdig/conf/htdig.conf\" -I../htlib -I../htcommon -I../db/dist -I../include -I/opt/ssl/include -g -O2 Retriever.cc c++ -c -DDEFAULT_CONFIG_FILE=\"/opt/www/htdig/conf/htdig.conf\" -I../htlib -I../htcommon -I../db/dist -I../include -I/opt/ssl/include -g -O2 SGMLEntities.cc c++ -c -DDEFAULT_CONFIG_FILE=\"/opt/www/htdig/conf/htdig.conf\" -I../htlib -I../htcommon -I../db/dist -I../include -I/opt/ssl/include -g -O2 Server.cc Server.cc: In method `Server::Server(char *, int, int, StringList * = 0)': Server.cc:44: passing `const char *' as argument 1 of `String::operator =(char *)' discards qualifiers make[1]: *** [Server.o] Error 1 make[1]: Leaving directory `/usr1/htdig/htdig-3.1.5/htdig' make: *** [all] Error 1 it0545:/usr1/htdig/htdig-3.1.5 # uname -a Linux somename 2.2.14 #1 Mon Mar 13 10:51:48 GMT 2000 i686 unknown it0545:/xxx/htdig/htdig-3.1.5 # gcc -v Reading specs from /usr/lib/gcc-lib/i486-suse-linux/2.95.2/specs gcc version 2.95.2 19991024 (release) To unsubscribe from the htdig mailing list, send a message to [EMAIL PROTECTED] You will receive a message to confirm this. List archives: http://www.htdig.org/mail/menu.html FAQ:http://www.htdig.org/FAQ.html
[htdig] ssl patch
Hi I just tried to patch htdig 3.1.5 with the ssl patch ftp://ftp.ccsf.org/htdig-patches/3.1.5/ssl.2 to a clean htdig. I got these errors root:/tmp/work/htdig-3.1.5# patch -p1 ../ssl.2 patching file `CONFIG' Hunk #1 FAILED at 8. 1 out of 1 hunk FAILED -- saving rejects to CONFIG.rej patching file `Makefile.config.in' Hunk #1 FAILED at 24. 1 out of 1 hunk FAILED -- saving rejects to Makefile.config.in.rej patching file `htcommon/DocumentDB.cc' Hunk #1 FAILED at 217. Hunk #2 FAILED at 284. 2 out of 2 hunks FAILED -- saving rejects to htcommon/DocumentDB.cc.rej patching file `htcommon/defaults.cc' Hunk #1 FAILED at 38. 1 out of 1 hunk FAILED -- saving rejects to htcommon/defaults.cc.rej patching file `htdig/Document.cc' Hunk #1 FAILED at 220. Hunk #2 FAILED at 332. 2 out of 2 hunks FAILED -- saving rejects to htdig/Document.cc.rej patching file `htdig/Images.cc' Hunk #1 FAILED at 61. Hunk #2 FAILED at 81. 2 out of 2 hunks FAILED -- saving rejects to htdig/Images.cc.rej patching file `htdig/Retriever.cc' Hunk #1 FAILED at 117. Hunk #2 FAILED at 132. Hunk #3 FAILED at 668. Hunk #4 FAILED at 1232. Hunk #5 FAILED at 1365. 5 out of 5 hunks FAILED -- saving rejects to htdig/Retriever.cc.rej patching file `htdig/Server.cc' Hunk #1 FAILED at 20. Hunk #2 FAILED at 40. 2 out of 2 hunks FAILED -- saving rejects to htdig/Server.cc.rej patching file `htdig/Server.h' Hunk #1 FAILED at 26. 1 out of 1 hunk FAILED -- saving rejects to htdig/Server.h.rej patching file `htlib/Connection.cc' Hunk #1 FAILED at 39. Hunk #2 FAILED at 53. Hunk #3 FAILED at 94. Hunk #4 FAILED at 119. Hunk #5 FAILED at 174. Hunk #6 FAILED at 251. Hunk #7 FAILED at 281. Hunk #8 FAILED at 426. Hunk #9 FAILED at 469. 9 out of 9 hunks FAILED -- saving rejects to htlib/Connection.cc.rej patching file `htlib/Connection.h' Hunk #1 FAILED at 36. Hunk #2 FAILED at 53. Hunk #3 FAILED at 73. Hunk #4 FAILED at 102. 4 out of 4 hunks FAILED -- saving rejects to htlib/Connection.h.rej patching file `htlib/URL.cc' Hunk #1 FAILED at 130. Hunk #2 FAILED at 223. Hunk #3 FAILED at 492. Hunk #4 FAILED at 549. 4 out of 4 hunks FAILED -- saving rejects to htlib/URL.cc.rej patching file `htlib/URL.h' Hunk #1 FAILED at 48. 1 out of 1 hunk FAILED -- saving rejects to htlib/URL.h.rej Am I doing something wrong??? Thanks begin:vcard n:Lyon;Jeremy tel;pager:303-899-9178 tel;work:303-624-4226 x-mozilla-html:FALSE org:Qwest;Information Technologies version:2.1 email;internet:[EMAIL PROTECTED] title:Associate IT Specialist adr;quoted-printable:;;1515 Arapahoe=0D=0ATower 1=0D=0AFlr 9;Denver;Colorado;80202; fn:Jeremy Lyon end:vcard To unsubscribe from the htdig mailing list, send a message to [EMAIL PROTECTED] You will receive a message to confirm this. List archives: http://www.htdig.org/mail/menu.html FAQ:http://www.htdig.org/FAQ.html
Re: [htdig] ssl patch
Add the -l flag to patch. I guess there is a white space issue. Joshua I just tried to patch htdig 3.1.5 with the ssl patch ftp://ftp.ccsf.org/htdig-patches/3.1.5/ssl.2 to a clean htdig. I got these errors root:/tmp/work/htdig-3.1.5# patch -p1 ../ssl.2 patching file `CONFIG' Hunk #1 FAILED at 8. 1 out of 1 hunk FAILED -- saving rejects to CONFIG.rej patching file `Makefile.config.in' Hunk #1 FAILED at 24. 1 out of 1 hunk FAILED -- saving rejects to Makefile.config.in.rej patching file `htcommon/DocumentDB.cc' Hunk #1 FAILED at 217. Hunk #2 FAILED at 284. 2 out of 2 hunks FAILED -- saving rejects to htcommon/DocumentDB.cc.rej patching file `htcommon/defaults.cc' Hunk #1 FAILED at 38. 1 out of 1 hunk FAILED -- saving rejects to htcommon/defaults.cc.rej patching file `htdig/Document.cc' Hunk #1 FAILED at 220. Hunk #2 FAILED at 332. 2 out of 2 hunks FAILED -- saving rejects to htdig/Document.cc.rej patching file `htdig/Images.cc' Hunk #1 FAILED at 61. Hunk #2 FAILED at 81. 2 out of 2 hunks FAILED -- saving rejects to htdig/Images.cc.rej patching file `htdig/Retriever.cc' Hunk #1 FAILED at 117. Hunk #2 FAILED at 132. Hunk #3 FAILED at 668. Hunk #4 FAILED at 1232. Hunk #5 FAILED at 1365. 5 out of 5 hunks FAILED -- saving rejects to htdig/Retriever.cc.rej patching file `htdig/Server.cc' Hunk #1 FAILED at 20. Hunk #2 FAILED at 40. 2 out of 2 hunks FAILED -- saving rejects to htdig/Server.cc.rej patching file `htdig/Server.h' Hunk #1 FAILED at 26. 1 out of 1 hunk FAILED -- saving rejects to htdig/Server.h.rej patching file `htlib/Connection.cc' Hunk #1 FAILED at 39. Hunk #2 FAILED at 53. Hunk #3 FAILED at 94. Hunk #4 FAILED at 119. Hunk #5 FAILED at 174. Hunk #6 FAILED at 251. Hunk #7 FAILED at 281. Hunk #8 FAILED at 426. Hunk #9 FAILED at 469. 9 out of 9 hunks FAILED -- saving rejects to htlib/Connection.cc.rej patching file `htlib/Connection.h' Hunk #1 FAILED at 36. Hunk #2 FAILED at 53. Hunk #3 FAILED at 73. Hunk #4 FAILED at 102. 4 out of 4 hunks FAILED -- saving rejects to htlib/Connection.h.rej patching file `htlib/URL.cc' Hunk #1 FAILED at 130. Hunk #2 FAILED at 223. Hunk #3 FAILED at 492. Hunk #4 FAILED at 549. 4 out of 4 hunks FAILED -- saving rejects to htlib/URL.cc.rej patching file `htlib/URL.h' Hunk #1 FAILED at 48. 1 out of 1 hunk FAILED -- saving rejects to htlib/URL.h.rej Am I doing something wrong??? Thanks To unsubscribe from the htdig mailing list, send a message to [EMAIL PROTECTED] You will receive a message to confirm this. List archives: http://www.htdig.org/mail/menu.html FAQ:http://www.htdig.org/FAQ.html
Re: [htdig] ssl patch
tried that and got the same errors Joshua Gerth wrote: Add the -l flag to patch. I guess there is a white space issue. Joshua I just tried to patch htdig 3.1.5 with the ssl patch ftp://ftp.ccsf.org/htdig-patches/3.1.5/ssl.2 to a clean htdig. I got these errors root:/tmp/work/htdig-3.1.5# patch -p1 ../ssl.2 patching file `CONFIG' Hunk #1 FAILED at 8. 1 out of 1 hunk FAILED -- saving rejects to CONFIG.rej patching file `Makefile.config.in' Hunk #1 FAILED at 24. 1 out of 1 hunk FAILED -- saving rejects to Makefile.config.in.rej patching file `htcommon/DocumentDB.cc' Hunk #1 FAILED at 217. Hunk #2 FAILED at 284. 2 out of 2 hunks FAILED -- saving rejects to htcommon/DocumentDB.cc.rej patching file `htcommon/defaults.cc' Hunk #1 FAILED at 38. 1 out of 1 hunk FAILED -- saving rejects to htcommon/defaults.cc.rej patching file `htdig/Document.cc' Hunk #1 FAILED at 220. Hunk #2 FAILED at 332. 2 out of 2 hunks FAILED -- saving rejects to htdig/Document.cc.rej patching file `htdig/Images.cc' Hunk #1 FAILED at 61. Hunk #2 FAILED at 81. 2 out of 2 hunks FAILED -- saving rejects to htdig/Images.cc.rej patching file `htdig/Retriever.cc' Hunk #1 FAILED at 117. Hunk #2 FAILED at 132. Hunk #3 FAILED at 668. Hunk #4 FAILED at 1232. Hunk #5 FAILED at 1365. 5 out of 5 hunks FAILED -- saving rejects to htdig/Retriever.cc.rej patching file `htdig/Server.cc' Hunk #1 FAILED at 20. Hunk #2 FAILED at 40. 2 out of 2 hunks FAILED -- saving rejects to htdig/Server.cc.rej patching file `htdig/Server.h' Hunk #1 FAILED at 26. 1 out of 1 hunk FAILED -- saving rejects to htdig/Server.h.rej patching file `htlib/Connection.cc' Hunk #1 FAILED at 39. Hunk #2 FAILED at 53. Hunk #3 FAILED at 94. Hunk #4 FAILED at 119. Hunk #5 FAILED at 174. Hunk #6 FAILED at 251. Hunk #7 FAILED at 281. Hunk #8 FAILED at 426. Hunk #9 FAILED at 469. 9 out of 9 hunks FAILED -- saving rejects to htlib/Connection.cc.rej patching file `htlib/Connection.h' Hunk #1 FAILED at 36. Hunk #2 FAILED at 53. Hunk #3 FAILED at 73. Hunk #4 FAILED at 102. 4 out of 4 hunks FAILED -- saving rejects to htlib/Connection.h.rej patching file `htlib/URL.cc' Hunk #1 FAILED at 130. Hunk #2 FAILED at 223. Hunk #3 FAILED at 492. Hunk #4 FAILED at 549. 4 out of 4 hunks FAILED -- saving rejects to htlib/URL.cc.rej patching file `htlib/URL.h' Hunk #1 FAILED at 48. 1 out of 1 hunk FAILED -- saving rejects to htlib/URL.h.rej Am I doing something wrong??? Thanks begin:vcard n:Lyon;Jeremy tel;pager:303-899-9178 tel;work:303-624-4226 x-mozilla-html:FALSE org:Qwest;Information Technologies version:2.1 email;internet:[EMAIL PROTECTED] title:Associate IT Specialist adr;quoted-printable:;;1515 Arapahoe=0D=0ATower 1=0D=0AFlr 9;Denver;Colorado;80202; fn:Jeremy Lyon end:vcard To unsubscribe from the htdig mailing list, send a message to [EMAIL PROTECTED] You will receive a message to confirm this. List archives: http://www.htdig.org/mail/menu.html FAQ:http://www.htdig.org/FAQ.html
Re: [htdig] ssl patch
On Thu, 16 Nov 2000, Jeremy Lyon wrote: Date: Thu, 16 Nov 2000 15:15:07 -0700 From: Jeremy Lyon [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: [htdig] ssl patch Hi I just tried to patch htdig 3.1.5 with the ssl patch ftp://ftp.ccsf.org/htdig-patches/3.1.5/ssl.2 to a clean htdig. I got these errors root:/tmp/work/htdig-3.1.5# patch -p1 ../ssl.2 Obviously you did not look at the patch;( The first lines read: # Tabs in this patch have been converted to spaces;( In order to apply the # patch to a clean htdig-3.1.5 please use the -l switch: # #gunzip -c htdig-3.1.5.tar.gz | tar xf - #cd htdig-3.1.5 #patch -p1 -l /path/to/ssl.2 ^ That ensures the patch to apply, but it does not guaranty that the package would compile; Michael Arndt [EMAIL PROTECTED] has testified about that;) If it does not compile on your system you might want to contact the author of the patch. You could find that information, also, in the patch: _ From [EMAIL PROTECTED] Sun Oct 29 11:11:32 2000 Date: Sun, 29 Oct 2000 15:24:01 -0500 From: Will Ballantyne [EMAIL PROTECTED] To: "J. op den Brouw" [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: [htdig] ssl patches for 3.1.5 _ Regards, Joe -- _/ _/_/_/ _/ __o _/ _/ _/ _/ __ _-\,_ _/ _/ _/_/_/ _/ _/ ..(_)/ (_) _/_/ oe _/ _/. _/_/ ah[EMAIL PROTECTED] To unsubscribe from the htdig mailing list, send a message to [EMAIL PROTECTED] You will receive a message to confirm this. List archives: http://www.htdig.org/mail/menu.html FAQ:http://www.htdig.org/FAQ.html
Re: [htdig] ssl patch
Dear Jeremy, I'm doing some research on people indexing data using SSL. Could you tell me a little more about your data? Is it just forms for entry, or is it personal or business records of some kind? Are you doing something interesting with security for the resulting index and search results? I'll be happy to let you know when I finish my report. Thanks, Avi At 3:15 PM -0700 11/16/2000, Jeremy Lyon wrote: Hi I just tried to patch htdig 3.1.5 with the ssl patch ftp://ftp.ccsf.org/htdig-patches/3.1.5/ssl.2 to a clean htdig. I got these errors -- _ Complete Guide to Search Engines for Web Sites, Intranets, and Portals: http://www.searchtools.com To unsubscribe from the htdig mailing list, send a message to [EMAIL PROTECTED] You will receive a message to confirm this. List archives: http://www.htdig.org/mail/menu.html FAQ:http://www.htdig.org/FAQ.html
[htdig] ssl Patch for htdig
Hello, i would need a SSL-Version of htdig. n the Archives i found a Thread about a SSL-Patch for htdig. Only Patchfile i found is: ftp://ftp.ccsf.org/htdig-patches/3.1.5/ssl.1 and that does not apply against a "clean htdig". Only Help would be aplying all patches manually. Is anyone out there who has done this already ? Or someone who can point me to a patch appliable against a clean htdig or send me patched sources ? merci Micha To unsubscribe from the htdig mailing list, send a message to [EMAIL PROTECTED] You will receive a message to confirm this. List archives: http://www.htdig.org/mail/menu.html FAQ:http://www.htdig.org/FAQ.html
Re: [htdig] ssl Patch for htdig
On Wed, 15 Nov 2000, Michael Arndt wrote: Date: Wed, 15 Nov 2000 13:56:05 +0100 From: Michael Arndt [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: [htdig] ssl Patch for htdig Hello, i would need a SSL-Version of htdig. n the Archives i found a Thread about a SSL-Patch for htdig. Only Patchfile i found is: ftp://ftp.ccsf.org/htdig-patches/3.1.5/ssl.1 and that does not apply against a "clean htdig". Only Help would be aplying all patches manually. Is anyone out there who has done this already ? Or someone who can point me to a patch appliable against a clean htdig or send me patched sources ? It was reported that the older patch: ftp://ftp.ccsf.org/htdig-patches/3.1.5/0ld/ssl.0 applies to a "clean htdig-3.1.5" with the -l switch: cd /path/to/htdig-3.1.5/ patch -p1 -l /path/to/ssl.0 Regards, Joe -- _/ _/_/_/ _/ __o _/ _/ _/ _/ __ _-\,_ _/ _/ _/_/_/ _/ _/ ..(_)/ (_) _/_/ oe _/ _/. _/_/ ah[EMAIL PROTECTED] To unsubscribe from the htdig mailing list, send a message to [EMAIL PROTECTED] You will receive a message to confirm this. List archives: http://www.htdig.org/mail/menu.html FAQ:http://www.htdig.org/FAQ.html
Re: [htdig] ssl Patch for htdig
On Wed, 15 Nov 2000, Joe R. Jah wrote: Date: Wed, 15 Nov 2000 10:26:20 -0800 (PST) From: "Joe R. Jah" [EMAIL PROTECTED] To: Michael Arndt [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [htdig] ssl Patch for htdig On Wed, 15 Nov 2000, Michael Arndt wrote: Date: Wed, 15 Nov 2000 13:56:05 +0100 From: Michael Arndt [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: [htdig] ssl Patch for htdig Hello, i would need a SSL-Version of htdig. n the Archives i found a Thread about a SSL-Patch for htdig. Only Patchfile i found is: ftp://ftp.ccsf.org/htdig-patches/3.1.5/ssl.1 and that does not apply against a "clean htdig". Only Help would be aplying all patches manually. Is anyone out there who has done this already ? Or someone who can point me to a patch appliable against a clean htdig or send me patched sources ? It was reported that the older patch: ftp://ftp.ccsf.org/htdig-patches/3.1.5/0ld/ssl.0 applies to a "clean htdig-3.1.5" with the -l switch: cd /path/to/htdig-3.1.5/ patch -p1 -l /path/to/ssl.0 OK, I downloaded htdig-3.1.5.tar.gz; my htdig have been patched and re-patched;) I tested both versions of the patch, and found out that ssl.1 does not apply, but ssl.0, the old patch applies with -l switch. I added the following lines to the beginning of the patch and placed it in the archives as: ftp://ftp.ccsf.org/htdig-patches/3.1.5/ssl.2 _ Tabs in this patch have been converted to spaces;( In order to apply the patch to a clean htdig-3.1.5 please use the -l switch: gunzip -c htdig-3.1.5.tar.gz | tar xf - cd htdig-3.1.5 patch -p1 -l /path/to/ssl.2 _ Regards, Joe -- _/ _/_/_/ _/ __o _/ _/ _/ _/ __ _-\,_ _/ _/ _/_/_/ _/ _/ ..(_)/ (_) _/_/ oe _/ _/. _/_/ ah[EMAIL PROTECTED] To unsubscribe from the htdig mailing list, send a message to [EMAIL PROTECTED] You will receive a message to confirm this. List archives: http://www.htdig.org/mail/menu.html FAQ:http://www.htdig.org/FAQ.html
Re: [htdig] ssl Patch for htdig
Speaking of ssl patches. I also downloaded 3.1.5 and patched it with the ssl.0 patch and the -l flag. However, I then ran into the additional problem that urls of the form: https://myserver.com were being directed to port 80, and that only urls of the form: https://myserver.com:433 were actually going to the encrypted port. So I hacked my copy so that any url which starts with https goes to port 433 by default but 'http' still goes to 80 by default. Of course, both can still be overridden by using the :port on the url. Did anyone else hit this? Would this patch be useful to anyone? If so I'll try to post it assuming I have the rights to do so. Joshua OK, I downloaded htdig-3.1.5.tar.gz; my htdig have been patched and re-patched;) I tested both versions of the patch, and found out that ssl.1 does not apply, but ssl.0, the old patch applies with -l switch. I added the following lines to the beginning of the patch and placed it in the archives as: ftp://ftp.ccsf.org/htdig-patches/3.1.5/ssl.2 _ Tabs in this patch have been converted to spaces;( In order to apply the patch to a clean htdig-3.1.5 please use the -l switch: gunzip -c htdig-3.1.5.tar.gz | tar xf - cd htdig-3.1.5 patch -p1 -l /path/to/ssl.2 _ To unsubscribe from the htdig mailing list, send a message to [EMAIL PROTECTED] You will receive a message to confirm this. List archives: http://www.htdig.org/mail/menu.html FAQ:http://www.htdig.org/FAQ.html
Re: [htdig] ssl Patch for htdig
errr make that 443 Joshua Speaking of ssl patches. I also downloaded 3.1.5 and patched it with the ssl.0 patch and the -l flag. However, I then ran into the additional problem that urls of the form: https://myserver.com were being directed to port 80, and that only urls of the form: https://myserver.com:433 were actually going to the encrypted port. So I hacked my copy so that any url which starts with https goes to port 433 by default but 'http' still goes to 80 by default. Of course, both can still be overridden by using the :port on the url. Did anyone else hit this? Would this patch be useful to anyone? If so I'll try to post it assuming I have the rights to do so. Joshua OK, I downloaded htdig-3.1.5.tar.gz; my htdig have been patched and re-patched;) I tested both versions of the patch, and found out that ssl.1 does not apply, but ssl.0, the old patch applies with -l switch. I added the following lines to the beginning of the patch and placed it in the archives as: ftp://ftp.ccsf.org/htdig-patches/3.1.5/ssl.2 _ Tabs in this patch have been converted to spaces;( In order to apply the patch to a clean htdig-3.1.5 please use the -l switch: gunzip -c htdig-3.1.5.tar.gz | tar xf - cd htdig-3.1.5 patch -p1 -l /path/to/ssl.2 _ To unsubscribe from the htdig mailing list, send a message to [EMAIL PROTECTED] You will receive a message to confirm this. List archives: http://www.htdig.org/mail/menu.html FAQ:http://www.htdig.org/FAQ.html To unsubscribe from the htdig mailing list, send a message to [EMAIL PROTECTED] You will receive a message to confirm this. List archives: http://www.htdig.org/mail/menu.html FAQ:http://www.htdig.org/FAQ.html
Re: [htdig] ssl Patch for htdig
On Wed, 15 Nov 2000, Joshua Gerth wrote: Date: Wed, 15 Nov 2000 13:38:29 -0800 (PST) From: Joshua Gerth [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: [htdig] ssl Patch for htdig Speaking of ssl patches. I also downloaded 3.1.5 and patched it with the ssl.0 patch and the -l flag. However, I then ran into the additional problem that urls of the form: https://myserver.com were being directed to port 80, and that only urls of the form: https://myserver.com:433 were actually going to the encrypted port. So I hacked my copy so that any url which starts with https goes to port 433 by default but 'http' still goes to 80 by default. Of course, both can still be overridden by using the :port on the url. Did anyone else hit this? Would this patch be useful to anyone? If so I'll try to post it assuming I have the rights to do so. I only tested to see if the patch applies to a clean 3.1.5. I am sure, however, that your patch will be useful to someone;) Go ahead an post it to the list, or just upload it to: ftp://ftp.ccsf.org/incoming/ P.S. It would be nice to document your patch; save potential users the guesswork and digging up relevant information in the list archives;) Regards, Joe -- _/ _/_/_/ _/ __o _/ _/ _/ _/ __ _-\,_ _/ _/ _/_/_/ _/ _/ ..(_)/ (_) _/_/ oe _/ _/. _/_/ ah[EMAIL PROTECTED] To unsubscribe from the htdig mailing list, send a message to [EMAIL PROTECTED] You will receive a message to confirm this. List archives: http://www.htdig.org/mail/menu.html FAQ:http://www.htdig.org/FAQ.html
[htdig] SSL patch for ht://Dig 3.1.5
Hi Brian, I am forwarding your message to the patch author and htdig users mailing list, to which the patch was originally posted. Maintainer of the patch site does not necessarily know why a patch fails; however, I have a pretty good idea in this case. All tab characters in the patch have been converted to spaces;( I checked the original mailing from Will; the tabs were converted there already. Regards, Joe -- _/ _/_/_/ _/__o _/ _/ _/ _/ __ _-\,_ _/ _/ _/_/_/ _/ _/ ..(_)/ (_) _/_/ oe _/ _/. _/_/ ah [EMAIL PROTECTED] -- Forwarded message -- Date: Tue, 31 Oct 2000 14:32:36 + (GMT) From: "Brian W. Spolarich" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: SSL patch for ht://Dig 3.1.5 I downloaded ht://Dig 3.1.5 from the htdig.org website and the SSL patch from: ftp://sol.ccsf.cc.ca.us/htdig-patches/3.1.5/ssl.0 I attempt to run 'patch' using the supplied patchfile and all of the patches fail. Am I missing something stupid and obvious? -bws admin1% tar zxf htdig-3.1.5.tar.gz admin1% ls htdig-3.1.5 htdig-3.1.5.tar.gz ssl.0 admin1% patch -p0 ssl.0 patching file `htdig-3.1.5/CONFIG' patching file `htdig-3.1.5/Makefile.config.in' Hunk #1 FAILED at 24. 1 out of 1 hunk FAILED -- saving rejects to htdig-3.1.5/Makefile.config.in.rej patching file `htdig-3.1.5/htcommon/DocumentDB.cc' Hunk #1 FAILED at 217. Hunk #2 FAILED at 284. 2 out of 2 hunks FAILED -- saving rejects to htdig-3.1.5/htcommon/DocumentDB.cc.rej patching file `htdig-3.1.5/htcommon/defaults.cc' Hunk #1 FAILED at 38. 1 out of 1 hunk FAILED -- saving rejects to htdig-3.1.5/htcommon/defaults.cc.rej patching file `htdig-3.1.5/htdig/Document.cc' Hunk #1 FAILED at 220. Hunk #2 FAILED at 332. 2 out of 2 hunks FAILED -- saving rejects to htdig-3.1.5/htdig/Document.cc.rej patching file `htdig-3.1.5/htdig/Images.cc' Hunk #1 FAILED at 61. Hunk #2 FAILED at 81. 2 out of 2 hunks FAILED -- saving rejects to htdig-3.1.5/htdig/Images.cc.rej patching file `htdig-3.1.5/htdig/Retriever.cc' Hunk #2 FAILED at 132. Hunk #3 FAILED at 668. Hunk #4 FAILED at 1232. Hunk #5 FAILED at 1365. 4 out of 5 hunks FAILED -- saving rejects to htdig-3.1.5/htdig/Retriever.cc.rej patching file `htdig-3.1.5/htdig/Server.cc' Hunk #1 succeeded at 20 with fuzz 1. Hunk #2 FAILED at 40. 1 out of 2 hunks FAILED -- saving rejects to htdig-3.1.5/htdig/Server.cc.rej patching file `htdig-3.1.5/htdig/Server.h' Hunk #1 FAILED at 26. 1 out of 1 hunk FAILED -- saving rejects to htdig-3.1.5/htdig/Server.h.rej patching file `htdig-3.1.5/htlib/Connection.cc' Hunk #1 FAILED at 39. Hunk #4 FAILED at 119. Hunk #5 FAILED at 174. Hunk #7 FAILED at 281. Hunk #9 FAILED at 469. 5 out of 9 hunks FAILED -- saving rejects to htdig-3.1.5/htlib/Connection.cc.rej patching file `htdig-3.1.5/htlib/Connection.h' Hunk #2 succeeded at 53 with fuzz 1. Hunk #3 succeeded at 73 with fuzz 2. Hunk #4 FAILED at 102. 1 out of 4 hunks FAILED -- saving rejects to htdig-3.1.5/htlib/Connection.h.rej patching file `htdig-3.1.5/htlib/URL.cc' Hunk #1 FAILED at 130. Hunk #2 FAILED at 223. Hunk #3 FAILED at 492. Hunk #4 FAILED at 549. 4 out of 4 hunks FAILED -- saving rejects to htdig-3.1.5/htlib/URL.cc.rej patching file `htdig-3.1.5/htlib/URL.h' Hunk #1 FAILED at 48. 1 out of 1 hunk FAILED -- saving rejects to htdig-3.1.5/htlib/URL.h.rej -- Brian W. Spolarich - Manager, Network Systems - WALID, Inc. - [EMAIL PROTECTED] Welcome to the Real World. - http://www.walid.com/ To unsubscribe from the htdig mailing list, send a message to [EMAIL PROTECTED] You will receive a message to confirm this. List archives: http://www.htdig.org/mail/menu.html FAQ:http://www.htdig.org/FAQ.html
[htdig] Re: [htdig3-dev] HTDIG SSL Patch
At 2:04 PM +0100 1/21/00, Browny wrote: We patched htdig 3.1.4 to support openssl. Now you can index http and https server as well. Thanks. I'm sure plenty of people will get some use out of it. Though the legal picture is changing somewhat, it may be some time before we can include any SSL-based code. The upcoming 3.2.0b1 release supports a mechanism for external transport methods, so this will allow htdig to use legal HTTPS mechanisms (among others). Cheers, -Geoff Hutchison Williams Students Online http://wso.williams.edu/ To unsubscribe from the htdig mailing list, send a message to [EMAIL PROTECTED] You will receive a message to confirm this.
