boa-devel Mailing List for Boa (Page 10)
Brought to you by:
jnelson
You can subscribe to this list here.
2000 |
Jan
(31) |
Feb
(42) |
Mar
(77) |
Apr
(8) |
May
(8) |
Jun
(16) |
Jul
|
Aug
(4) |
Sep
(20) |
Oct
(1) |
Nov
(11) |
Dec
(1) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
|
Feb
(9) |
Mar
(3) |
Apr
|
May
(3) |
Jun
|
Jul
(3) |
Aug
|
Sep
(5) |
Oct
|
Nov
(1) |
Dec
(1) |
2002 |
Jan
(2) |
Feb
|
Mar
|
Apr
(4) |
May
|
Jun
|
Jul
(1) |
Aug
(2) |
Sep
(7) |
Oct
(15) |
Nov
(6) |
Dec
(41) |
2003 |
Jan
(32) |
Feb
(20) |
Mar
(1) |
Apr
(1) |
May
(3) |
Jun
(1) |
Jul
(9) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(12) |
2004 |
Jan
(2) |
Feb
(5) |
Mar
(5) |
Apr
(1) |
May
(10) |
Jun
(3) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(2) |
2005 |
Jan
(1) |
Feb
|
Mar
|
Apr
(2) |
May
(1) |
Jun
(2) |
Jul
|
Aug
(1) |
Sep
(2) |
Oct
|
Nov
(2) |
Dec
(8) |
2006 |
Jan
(10) |
Feb
(3) |
Mar
(1) |
Apr
(1) |
May
(6) |
Jun
(13) |
Jul
(12) |
Aug
(13) |
Sep
(4) |
Oct
(23) |
Nov
(29) |
Dec
(26) |
2007 |
Jan
(15) |
Feb
(19) |
Mar
(29) |
Apr
(79) |
May
(74) |
Jun
(112) |
Jul
(44) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: <all...@li...> - 2003-02-03 06:00:18
|
Has anyone thought about a faster alternative to CGI for serving dynamic content with boa? I am aware of the general approach of embedding an interpreter in the web server, and there is of course fastcgi which is scary in a different way. Neither seem compatible to small is good philosophy. What would be? /Allan --=20 Allan Wind P.O. Box 2022 Woburn, MA 01888-0022 USA |
From: <all...@li...> - 2003-02-03 05:41:14
|
On 2003-01-23 09:32:00, dmahurin wrote: > Change VirtualHost from a logical switch to one that takes a parameter of= =20 > "ip", "name" or possibly "both". With no parameter, it defaults to "ip", = to=20 > be compatible with the current behavior. "hostname" might be more descriptive than "name", and I suggest adding "interface" to the mix. It would probably be cleaner to accept multiple VirtualHost options or just allow an ordered list as the argument that then map appropiately to the directory structure (interface,hostname=20 would be ideal for me, while others may simply want hostname). Let's not lose the feature we have now, which allows us to serve different content based on the interface the request came in on (if either ip or interface is given). It might be worth thinking about hashing to keep a small number of entries in directories i.e. hash(hostname) (and may hash(ip)). We probably do not want the flxibility of mod_vhost_alias.html, a simple user defined function might do although regex would be groovy :-) > Also relative paths in Alias and ScriptAlias should be made relative to t= he=20 > effective document root. >=20 > With "ScriptAlias /cgi-bin abc/cgi-bin", > and "VirtualHost name", Good idea, but I am not sure that I like the relative paths. What about using the same mapping as specified in the VirtualHost option so: VirtualHost ip,hostname ScriptAlias /usr/local/lib/cgi-bin /cgi-bin would mean that we check in /usr/local/lib/cgi-bin/ip/hostname, then /usr/local/lib/cgi-bin/ip and finally /usr/local/lib/cgi-bin (again, retain the seperation between ip/interfaces). Not sure if this would cause performance issues though. I would love to work on this at some point, but I pressed for time, so if anyone is interested please feel free. /Allan --=20 Allan Wind P.O. Box 2022 Woburn, MA 01888-0022 USA |
From: Jon N. <jn...@ja...> - 2003-01-31 21:55:16
|
On Fri, 31 Jan 2003, Chris Brennan wrote: > Trying to compile boa on an HP-UX 9000 box, I get the following: > > I googled a few strings and found nobody with similar problems.. > > Any ideas? Thanks very much. Give 0.94.14rc13 a try. 0.94.14+ gets rid of lex and yacc. 0.94.14 is very close to release. In fact, unless somebody reports problems with rc13, I'll probably release 0.94.14 sometime this weekend, or early next week. -- Democracy is two wolves and a sheep voting on what to have for dinner. Liberty is two wolves attempting to have a sheep for dinner and finding a well-informed, well-armed sheep. Jon Nelson <jn...@ja...> C and Python Code Gardener |
From: Chris B. <sou...@un...> - 2003-01-31 21:31:23
|
Trying to compile boa on an HP-UX 9000 box, I get the following: I googled a few strings and found nobody with similar problems.. Any ideas? Thanks very much. -Chris <---------------------------SNIP-------------------------------------> kilo:root> pwd /mnt1/boa-0.94.13/src kilo:root> ./configure ... creating ./config.status creating Makefile creating config.h kilo:root> make yacc -d boa_grammar.y gcc -g -O2 -pipe -Wall -I. -c -o y.tab.o y.tab.c boa_grammar.y: In function `yyparse': boa_grammar.y:475: warning: implicit declaration of function `yylex' boa_grammar.y:576: warning: label `yyerrlab' defined but not used boa_grammar.y:386: warning: label `yynewstate' defined but not used lex boa_lexer.l "boa_lexer.l" line 77: warning 37: Definition \" { /* saw closing quote - all done */ BEGIN(INITIAL); *string_buf_ptr = '\0'; /* return string constant token type and value to parser */ yylval.sval = string_buf; return STRING; not found "boa_lexer.l" line 78: error 81: syntax error make: *** [lex.yy.c] Error 1 |
From: Jon N. <jn...@ja...> - 2003-01-30 18:51:34
|
I converted the texinfo docs to docbook xml, and using xsltproc, generated the documentation at: http://www.boa.org/new_docs/ Please give it a look. -- Democracy is two wolves and a sheep voting on what to have for dinner. Liberty is two wolves attempting to have a sheep for dinner and finding a well-informed, well-armed sheep. Jon Nelson <jn...@ja...> C and Python Code Gardener |
From: Jon N. <jn...@ja...> - 2003-01-23 22:14:41
|
This is 0.94.14rc13. This release improves select and poll somewhat, and helps to avoid out-of-file errors as well. It also fixes the __func__ support introduced with rc12. The relevant additions to the changelog are: * force select and poll to always be included in dependency stuff * fix use of HAVE_FUNC * if FD_SETSIZE is undefined, set MAX_FD to OPEN_MAX instead of arbitarily setting it to 2048. * improve the poll code slightly * give Boa more breathing room WRT MaxConnections and total current connections -- currently simply set at 20. * forcibly clear the server_s from the block_read_fdset when it won't be checked. -- Democracy is two wolves and a sheep voting on what to have for dinner. Liberty is two wolves attempting to have a sheep for dinner and finding a well-informed, well-armed sheep. Jon Nelson <jn...@ja...> C and Python Code Gardener |
From: dmahurin <dma...@be...> - 2003-01-23 19:20:34
|
My suggestion for name and ip based virtual hosts is the following:: Change VirtualHost from a logical switch to one that takes a parameter of= =20 "ip", "name" or possibly "both". With no parameter, it defaults to "ip", = to=20 be compatible with the current behavior. If ip is specified, then the referenced ip would be appended to the effec= tive=20 document root. if name is specified then the referenced name would be appended to the=20 effective document root. If the directory corresponding to ip or name does not exist and a directo= ry=20 "default" does exist, it would be used instead. Also relative paths in Alias and ScriptAlias should be made relative to t= he=20 effective document root. With "ScriptAlias /cgi-bin abc/cgi-bin", and "VirtualHost name", request of / to ip me.dyn.net would translate to: DocumentRoot/me.dyn.net/ request of /cgi-bin/x.cgi would translate to: DocumentRoot/me.dyn.net/xyz/cgi-bin. With the change to "VirtualHost ip", the same requests to ip a.b.c.d tran= slate=20 to: DocumentRoot/a.b.c.d/ DocumentRoot/a.b.c.d/xyz/cgi-bin/ With the change to "VirtualHost both", the same requests to ip a.b.c.d=20 translate to: DocumentRoot/a.b.c.d/me.dyn.net/ DocumentRoot/a.b.c.d/me.dyn.net/xyz/cgi-bin/ Also, with both specified, should could have a directory structure in=20 DocumentRoot like: DocumentRoot/ =09127.0.0.1/default/ - localhost specified with any name =09201.202.203.204/ =09=09toast.dyn.net/ - request to only this ip and name =09201.202.203.205/ =09=09default/ - requests to 201.202.203.205, any name. =09default/ =09=09me.dyn.net/ - any ip named me.dyn.net/ =09=09home.dyn.net/ - any ip named home.dyn.net/ =09=09default/ - default ip/name Of course "both" can be implemented later. -don On Thursday 23 January 2003 06:56 am, Allan Wind wrote: > On 2003-01-23 06:44:15, Jon Nelson wrote: > > On Thu, 23 Jan 2003, Allan Wind wrote: > > > I need virtual host support that is not tied to the ip (as I am on = dhcp > > > and hence it might change on me). Can we steel the code from hydra= or > > > are there other plans? > > |
From: Jon N. <jn...@ja...> - 2003-01-23 17:29:41
|
On Thu, 23 Jan 2003, Allan Wind wrote: > On 2003-01-23 06:44:15, Jon Nelson wrote: > > On Thu, 23 Jan 2003, Allan Wind wrote: > > > > > I need virtual host support that is not tied to the ip (as I am on dhcp > > > and hence it might change on me). Can we steel the code from hydra or > > > are there other plans? > > > > Can you be more specific? > > Not sure what you want more details on, Jon. But basicly I have a > requirement for multiple sites being serviced (in my case, localhost and > lifeintegrity.com) which result in a directory structure like this: > > DocumentRoot/127.0.0.1 > DocumentRoot/$IP > > (When I played it with last yesterday, it seem that if you hit the one > interface, you cannot get to the content associated with the other. > Nifty!) That's a side effect of using the IP as (part of) the base for the content root. > Now in the (unlikely) event that I get a new IP ($IP2), I assume that > boa will continue to listen on all interfaces but would look in: > > DocumentRoot/$IP2 > > instead of: > > DocumentRoot/$IP > > Instead of moving the directory around and bouncing boa, I want name > (or really interface) based virtual hosting, e.g.: > > DocumentRoot/localhost (or lo) > DocumentRoot/lifeintegrity.com (or eth0) > > I noticed in the announcement earlier for the hydro project, that they > already have named based virtual hosting implemented. Can we integrate > those changes into boa or is there a particular reason why we have not > done so already? Boa also has name-based virtualhosting, but it uses IPs as well. someroot/$ip/$hostname/stuff_here > Could run two instances and not use VirtualHost of course ;-) That is what I would do right now, but your suggestion is interesting -- it's name-based virtualhosting *without* using the IP. > Is there any reason why boa takes a RootDirectory argument instead of an > argument to a config file? Historical, that's all. Somewhere in the 0.94.14 rc series the '-f' flag was added to specify a config file, but even then Boa will want to chdir *somewhere*. I feel -f is acceptable but not recommended, but I also understand it has its place, too. -- Democracy is two wolves and a sheep voting on what to have for dinner. Liberty is two wolves attempting to have a sheep for dinner and finding a well-informed, well-armed sheep. Jon Nelson <jn...@ja...> C and Python Code Gardener |
From: <all...@li...> - 2003-01-23 14:56:40
|
On 2003-01-23 06:44:15, Jon Nelson wrote: > On Thu, 23 Jan 2003, Allan Wind wrote: >=20 > > I need virtual host support that is not tied to the ip (as I am on dhcp > > and hence it might change on me). Can we steel the code from hydra or > > are there other plans? >=20 > Can you be more specific? Not sure what you want more details on, Jon. But basicly I have a requirement for multiple sites being serviced (in my case, localhost and lifeintegrity.com) which result in a directory structure like this: DocumentRoot/127.0.0.1 DocumentRoot/$IP (When I played it with last yesterday, it seem that if you hit the one interface, you cannot get to the content associated with the other. Nifty!) Now in the (unlikely) event that I get a new IP ($IP2), I assume that boa will continue to listen on all interfaces but would look in: DocumentRoot/$IP2 instead of: DocumentRoot/$IP Instead of moving the directory around and bouncing boa, I want name (or really interface) based virtual hosting, e.g.: DocumentRoot/localhost (or lo) DocumentRoot/lifeintegrity.com (or eth0) I noticed in the announcement earlier for the hydro project, that they already have named based virtual hosting implemented. Can we integrate those changes into boa or is there a particular reason why we have not done so already? Could run two instances and not use VirtualHost of course ;-) Is there any reason why boa takes a RootDirectory argument instead of an argument to a config file? /Allan --=20 Allan Wind P.O. Box 2022 Woburn, MA 01888-0022 USA |
From: Jon N. <jn...@ja...> - 2003-01-23 13:32:50
|
On Thu, 23 Jan 2003, Allan Wind wrote: > I need virtual host support that is not tied to the ip (as I am on dhcp > and hence it might change on me). Can we steel the code from hydra or > are there other plans? Can you be more specific? -- Democracy is two wolves and a sheep voting on what to have for dinner. Liberty is two wolves attempting to have a sheep for dinner and finding a well-informed, well-armed sheep. Jon Nelson <jn...@ja...> C and Python Code Gardener |
From: <all...@li...> - 2003-01-23 08:03:45
|
I need virtual host support that is not tied to the ip (as I am on dhcp and hence it might change on me). Can we steel the code from hydra or are there other plans? /Allan --=20 Allan Wind P.O. Box 2022 Woburn, MA 01888-0022 USA |
From: <all...@li...> - 2003-01-23 07:55:52
|
On 2003-01-06 10:52:00, Jon Nelson wrote: > OK. I can't really think of a practical way to do this with Boa without > code modification. I decided to let the client handle it for now with a meta tag: <meta http-equiv=3D"refresh" content=3D"0;url=3Dhttp://www.lifeintegrity.co= m/home/index.html"> while realizing that it might break for some browsers. > As for redirecting ^/$ to /home/ (not /home, because that in itself > will generate yet-another 30x series redirection because it's a > directory that doesn't end in a '/'), I'm sure a tiny bit of code > modification could be done. If I add regex support, would it seriously be considered for inclusion? /Allan --=20 Allan Wind P.O. Box 2022 Woburn, MA 01888-0022 USA |
From: Jon N. <jn...@ja...> - 2003-01-22 18:04:21
|
Index: src/log.c =================================================================== RCS file: /home/jnelson/cvs/boa/src/log.c,v retrieving revision 1.36.2.17 diff -u -r1.36.2.17 log.c --- src/log.c 20 Jan 2003 17:59:26 -0000 1.36.2.17 +++ src/log.c 22 Jan 2003 17:18:32 -0000 @@ -260,7 +260,10 @@ void log_error_mesg(const char *file, const int line, const char *func, const char *mesg) { int errno_save = errno; - fprintf(stderr, "%s%s:%d (%s) - ", get_commonlog_time(), file, line, func); + if (func) + fprintf(stderr, "%s%s:%d (%s) - ", get_commonlog_time(), file, line, func); + else + fprintf(stderr, "%s%s:%d - ", get_commonlog_time(), file, line); errno = errno_save; perror(mesg); errno = errno_save; On Wed, 22 Jan 2003, Jon Nelson wrote: > Good Catch! I'll make that change in CVS right away. > > On Wed, 22 Jan 2003, Peter Korsgaard wrote: > > > >>>>> "Jon" == Jon Nelson <jn...@ja...> writes: > > > > Hi, > > > > Jon> * check for and use __func__, a C99 construct that is used in > > Jon> the DIE and WARN macros to also describe the name of the current > > Jon> function. > > > > From src/defines.h: > > #ifdef HAVE_FUNC > > #define DIE(mesg) log_error_mesg(__FILE__, __LINE__, __func__, mesg), exit(1) > > #define WARN(mesg) log_error_mesg(__FILE__, __LINE__, __func__, mesg) > > #else > > #define DIE(mesg) log_error_mesg(__FILE__, __LINE__, NULL, mesg), exit(1) > > #define WARN(mesg) log_error_mesg(__FILE__, __LINE__, NULL, mesg) > > #endif > > > > And src/log.c: > > void log_error_mesg(const char *file, const int line, const char *func, > > const char *mesg) > > { > > int errno_save = errno; > > fprintf(stderr, "%s%s:%d (%s) - ", get_commonlog_time(), file, line, func); > > > > Is it valid to give fprintf a NULL pointer for a %s string on all > > systems? info libc says: > > > > If you accidentally pass a null pointer as the argument for a `%s' > > conversion, the GNU library prints it as `(null)'. We think this is > > more useful than crashing. But it's not good practice to pass a null > > argument intentionally. > > > > Perhaps it would be safer to replace the NULL with "", "N/A", > > "Unknown" or similiar. > > > > -- > > Bye, Peter Korsgaard > > > > > > -- > Democracy is two wolves and a sheep voting on what to have for dinner. > Liberty is two wolves attempting to have a sheep for dinner and > finding a well-informed, well-armed sheep. > > Jon Nelson <jn...@ja...> > C and Python Code Gardener > > > ------------------------------------------------------- > This SF.net email is sponsored by: Scholarships for Techies! > Can't afford IT training? All 2003 ictp students receive scholarships. > Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. > www.ictp.com/training/sourceforge.asp > _______________________________________________ > Boa-devel mailing list > Boa...@li... > https://lists.sourceforge.net/lists/listinfo/boa-devel > > -- Democracy is two wolves and a sheep voting on what to have for dinner. Liberty is two wolves attempting to have a sheep for dinner and finding a well-informed, well-armed sheep. Jon Nelson <jn...@ja...> C and Python Code Gardener |
From: Jon N. <jn...@ja...> - 2003-01-22 18:00:47
|
Good Catch! I'll make that change in CVS right away. On Wed, 22 Jan 2003, Peter Korsgaard wrote: > >>>>> "Jon" == Jon Nelson <jn...@ja...> writes: > > Hi, > > Jon> * check for and use __func__, a C99 construct that is used in > Jon> the DIE and WARN macros to also describe the name of the current > Jon> function. > > From src/defines.h: > #ifdef HAVE_FUNC > #define DIE(mesg) log_error_mesg(__FILE__, __LINE__, __func__, mesg), exit(1) > #define WARN(mesg) log_error_mesg(__FILE__, __LINE__, __func__, mesg) > #else > #define DIE(mesg) log_error_mesg(__FILE__, __LINE__, NULL, mesg), exit(1) > #define WARN(mesg) log_error_mesg(__FILE__, __LINE__, NULL, mesg) > #endif > > And src/log.c: > void log_error_mesg(const char *file, const int line, const char *func, > const char *mesg) > { > int errno_save = errno; > fprintf(stderr, "%s%s:%d (%s) - ", get_commonlog_time(), file, line, func); > > Is it valid to give fprintf a NULL pointer for a %s string on all > systems? info libc says: > > If you accidentally pass a null pointer as the argument for a `%s' > conversion, the GNU library prints it as `(null)'. We think this is > more useful than crashing. But it's not good practice to pass a null > argument intentionally. > > Perhaps it would be safer to replace the NULL with "", "N/A", > "Unknown" or similiar. > > -- > Bye, Peter Korsgaard > > -- Democracy is two wolves and a sheep voting on what to have for dinner. Liberty is two wolves attempting to have a sheep for dinner and finding a well-informed, well-armed sheep. Jon Nelson <jn...@ja...> C and Python Code Gardener |
From: Peter K. <ja...@su...> - 2003-01-22 17:56:13
|
>>>>> "Jon" == Jon Nelson <jn...@ja...> writes: Hi, Jon> * check for and use __func__, a C99 construct that is used in Jon> the DIE and WARN macros to also describe the name of the current Jon> function. From src/defines.h: #ifdef HAVE_FUNC #define DIE(mesg) log_error_mesg(__FILE__, __LINE__, __func__, mesg), exit(1) #define WARN(mesg) log_error_mesg(__FILE__, __LINE__, __func__, mesg) #else #define DIE(mesg) log_error_mesg(__FILE__, __LINE__, NULL, mesg), exit(1) #define WARN(mesg) log_error_mesg(__FILE__, __LINE__, NULL, mesg) #endif And src/log.c: void log_error_mesg(const char *file, const int line, const char *func, const char *mesg) { int errno_save = errno; fprintf(stderr, "%s%s:%d (%s) - ", get_commonlog_time(), file, line, func); Is it valid to give fprintf a NULL pointer for a %s string on all systems? info libc says: If you accidentally pass a null pointer as the argument for a `%s' conversion, the GNU library prints it as `(null)'. We think this is more useful than crashing. But it's not good practice to pass a null argument intentionally. Perhaps it would be safer to replace the NULL with "", "N/A", "Unknown" or similiar. -- Bye, Peter Korsgaard |
From: Jon N. <jn...@ja...> - 2003-01-22 14:40:38
|
This is pretty much a minor clean up release -- a new directive, 'DefaultCharset' has been added, boa.texi has been updated to include some missing directives, and some otherwise fairly minor changes have been made. The relevant additions to the changelog are: * check for and use __func__, a C99 construct that is used in the DIE and WARN macros to also describe the name of the current function. * fix a very minor IPv6 issue, and include netdb.h in compat.h so that NI_MAXHOST is defined for IPv6 * when we can't mmap a file, fall back to IOSHUFFLE. If we couldn't mmap the file due to an error in mmap or madvise, report the error, otherwise it is safe to assume we simply ran out of hash table space. * The following 2 changes borrowed from Hydra (which is itself based on Boa): * Some optimizations in HTTP header parsing. * Added DefaultCharset configuration directive. The default character set given, will be appended to all text mime types. * update boa.texi with some missing configuration directives -- Democracy is two wolves and a sheep voting on what to have for dinner. Liberty is two wolves attempting to have a sheep for dinner and finding a well-informed, well-armed sheep. Jon Nelson <jn...@ja...> C and Python Code Gardener |
From: <te...@ad...> - 2003-01-15 22:33:22
|
El 15-Jan-2003 a las 15:56:44, Jon Nelson escribi=F3: > On Wed, 15 Jan 2003, [iso-8859-15] Te=F3filo Ruiz Su=E1rez wrote: >=20 > > Hi there. I am the one adopting the boa Debian package :-) I think we > > are going to read each other often... >=20 > Hi! Hi Jon :] > > I would like to enable the IPv6 support in the package to fix a bug in > > the Debian Bug Tracking System [0]. I have already tried patching the > > code with the little patch sent by the reporter [1], but boa says this: >=20 > .. >=20 > IPv6 support seems to work fine locally without any patching, when > compiled with "CFLAGS=3D-DINET6 -Wall -O2" ./configure >=20 > The IPv6 support in Boa is not very well understood. > Is IPv6 support a requirement for Debian? If not, don't try to enable it > if it doesn't work. It is not, I will try with that cflags :) Anyway, if it is not well understood, I just should to explain how to enable it in the README.Debian.=20 > Regarding Debian bugs. > Bug 146363 is most certainly *not* a Boa bug. Right. > Bug 175153 has been fixed in CVS, and the fix will first appear in > 0.94.14. Looking forward 0.94.14 :-) > The patch for bug 175151 looks OK, I'll have to look it over, but that, > too might end up in 0.94.14. Go 4 lines above :-P > 135751 was not reproduceable, and should probably be closed. > It can always be reopened again if it shows up. Right. > In the meantime, I'll look into the IPv6 thing. Thank you so much. Well, I'm going to close the bugs fixed as soon as I upload the new version.=20 Thank you, again. --=20 Te=F3filo Ruiz Su=E1rez || (teo) || Sevilla, Espa=F1a=20 -------------------------------------------------------- te...@ad... <-> teo...@hi...=09 -------------------------------------------------------- GnuPG Key ID: 420718E6 FPR: 0280 862C 064B FA76 9A1C EB64 5755 A66C 4207 18E6 |
From: Jon N. <jn...@ja...> - 2003-01-15 22:22:14
|
On Wed, 15 Jan 2003, [iso-8859-15] Te=F3filo Ruiz Su=E1rez wrote: > Hi there. I am the one adopting the boa Debian package :-) I think we > are going to read each other often... Hi! =20 > I would like to enable the IPv6 support in the package to fix a bug in > the Debian Bug Tracking System [0]. I have already tried patching the > code with the little patch sent by the reporter [1], but boa says this: =2E. IPv6 support seems to work fine locally without any patching, when compiled with "CFLAGS=3D-DINET6 -Wall -O2" ./configure The IPv6 support in Boa is not very well understood. Is IPv6 support a requirement for Debian? If not, don't try to enable it if it doesn't work. Regarding Debian bugs. Bug 146363 is most certainly *not* a Boa bug. Bug 175153 has been fixed in CVS, and the fix will first appear in 0.94.14. The patch for bug 175151 looks OK, I'll have to look it over, but that, too might end up in 0.94.14. 135751 was not reproduceable, and should probably be closed. It can always be reopened again if it shows up. In the meantime, I'll look into the IPv6 thing. -- Democracy is two wolves and a sheep voting on what to have for dinner.=20 Liberty is two wolves attempting to have a sheep for dinner and finding a well-informed, well-armed sheep.=20 Jon Nelson <jn...@ja...> C and Python Code Gardener |
From: <te...@ad...> - 2003-01-15 22:04:36
|
Hi there. I am the one adopting the boa Debian package :-) I think we are going to read each other often... I would like to enable the IPv6 support in the package to fix a bug in the Debian Bug Tracking System [0]. I have already tried patching the code with the little patch sent by the reporter [1], but boa says this: [14/Jan/2003:23:48:24 +0000] boa.c:173 - unable to create socket: Address f= amily not supported by protocol Another thing I look for help it is with this other bug about the icky kernel bug test [2]. Thanks a lot in advance ;-) [0] http://bugs.debian.org/175165 [1] Attached [2] http://bugs.debian.org/175165=20 --=20 Te=F3filo Ruiz Su=E1rez || (teo) || Sevilla, Espa=F1a=20 -------------------------------------------------------- te...@ad... <-> teo...@hi...=09 -------------------------------------------------------- GnuPG Key ID: 420718E6 FPR: 0280 862C 064B FA76 9A1C EB64 5755 A66C 4207 18E6 |
From: Jon N. <jn...@ja...> - 2003-01-14 06:27:51
|
And it fixes 'HEAD' method requests, and the annoying "connection timed out bug" as well. Also, a *huge* (54KB) patch went in to change many signed ints to unsigned ints, add the "const" and "static" keywords where appropriate, and make otherwise very few changes. -- Democracy is two wolves and a sheep voting on what to have for dinner. Liberty is two wolves attempting to have a sheep for dinner and finding a well-informed, well-armed sheep. Jon Nelson <jn...@ja...> C and Python Code Gardener |
From: <0...@pe...> - 2003-01-14 03:19:07
|
I tried the patch from "Minor issue with rc9" and it doesn't seem to fix it: 64.68.82.58 - - [14/Jan/2003:00:00:29 +=A6211] request "(null)" ("(null)"):= connection timed out 64.68.82.74 - - [14/Jan/2003:00:10:19 +=A6211] request "(null)" ("(null)"):= connection timed out 64.68.82.71 - - [14/Jan/2003:00:29:20 +=A6211] request "(null)" ("(null)"):= connection timed out 127.0.0.1 - - [14/Jan/2003:01:11:21 +=A6211] "GET /index.foo.html" 404 0 "-= " "-" 127.0.0.1 - - [14/Jan/2003:01:11:21 +=A6211] request "(null)" ("(null)"): c= onnection timed out 127.0.0.1 - - [14/Jan/2003:01:11:21 +=A6211] request "GET /index.foo.html" = ("/cygdrive/g/index.foo.html"): document open: No such file or directory --=20 0@pervalidus.{net, {dyndns.}org} |
From: <0...@pe...> - 2003-01-13 13:26:56
|
I keep getting the above in error_log, though I don't see anything wrong. 127.0.0.1 - - [13/Jan/2003:10:59:25 +=A6211] "GET /index.foo.html" 404 0 "-= " "-" 127.0.0.1 - - [13/Jan/2003:10:59:25 +=A6211] request "(null)" ("(null)"): c= onnection timed out 127.0.0.1 - - [13/Jan/2003:10:59:25 +=A6211] request "GET /index.foo.html" = ("/cygdrive/g/index.foo.html"): document open: No such file or directory 200.255.184.111 - - [12/Jan/2003:17:34:38 +=A6211] "GET /Windows/devel/brow= sers/lynx/" 302 0 "-" "-" 200.255.184.111 - - [12/Jan/2003:17:34:37 +=A6211] request "(null)" ("(null= )"): connection timed out And what about the following ? 62.168.105.2 - - [12/Jan/2003:20:43:04 +=A6211] "GET /browsers/lynx/downloa= d/lynx-cygwin-static.exe.bz2 HTTP/1.0" 206 34560 "-" "Wget/1.7" buffer flush: Connection aborted 62.168.105.2 - - [12/Jan/2003:20:43:04 +=A6211] request "(null)" ("(null)")= : header read: Connection aborted 0.94.14rc10 on latest Cygwin. --=20 0@pervalidus.{net, {dyndns.}org} |
From: Jon N. <jn...@ja...> - 2003-01-10 21:43:59
|
On 10 Jan 2003, Peter Korsgaard wrote: > Hi, > > rc10 seems to be working fine here, but I noticed that the > documentation is not completely uptodate/correct. Here is a small > patch which corrects it. > > http://peter.korsgaard.com/software/boa.doc.0.94.14rc10.patch Cool. Thanks, and applied as-is. -- Democracy is two wolves and a sheep voting on what to have for dinner. Liberty is two wolves attempting to have a sheep for dinner and finding a well-informed, well-armed sheep. Jon Nelson <jn...@ja...> C and Python Code Gardener |
From: Peter K. <ja...@su...> - 2003-01-10 21:02:08
|
Hi, rc10 seems to be working fine here, but I noticed that the documentation is not completely uptodate/correct. Here is a small patch which corrects it. http://peter.korsgaard.com/software/boa.doc.0.94.14rc10.patch -- Bye, Peter Korsgaard |
From: Jon N. <jn...@ja...> - 2003-01-10 18:04:23
|
and is available on the website. -- Democracy is two wolves and a sheep voting on what to have for dinner. Liberty is two wolves attempting to have a sheep for dinner and finding a well-informed, well-armed sheep. Jon Nelson <jn...@ja...> C and Python Code Gardener |