We have made SSL support opt-in, so in this case the bug is that hacker-news tries to use a https URL without having loaded "urls.secure". Probably we should handle this in an automatic way when an https url is requested, but for now this is fixed in this patch:
https://github.com/slavapestov/factor/commit/a1a9326307e68e6c981b7d9ac601abab4afbe3bd Thanks for the report. On Sun, Oct 25, 2015 at 1:23 PM, Sankaranarayanan Viswanathan < rationalrev...@gmail.com> wrote: > Hi, > > I'm running the latest factor (commit > 753ebb15829543ecbef23fae8a7cbbf572d45225). > > I was trying out the hacker-news vocab in extra, and I came across an error > running the hacker-news. > word: > Generic word >secure-addr does not define a method for the inet class. > Dispatching on object: T{ inet f "hacker-news.firebaseio.com" 443 } > > Following the definition of url-addr, I see towards the end of > "urls.private" > vocab source code: { "urls" "io.sockets.secure" } "urls.secure" > require-when > > So, it seems like some thing was responsible to load "io.sockets.secure" > (which > would have caused "urls.secure" to load) but did not. > > So, in the listener, I load the vocab io.sockets.secure: > USE: io.sockets.secure > Looking at the output in the listener, I can see that loading this vocab > caused "urls.secure" to load. > > After this executing the hacker-news. word in the listener runs without > error. > > Is this a bug? > > Thanks, > Sankar > > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Factor-talk mailing list > Factor-talk@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/factor-talk >
------------------------------------------------------------------------------
_______________________________________________ Factor-talk mailing list Factor-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/factor-talk
