Re: Re: cannot get node deployed on Ubuntu Lucid

I realize node-router is not causing the 403, just that it is 
redirecting to different pages and somewhere nginx is not getting to or 
has wrong permissions.

thks Tim for the sample config.

If I run curl with the domain I get html with "301 Moved Permanently"

I don't understand where the add_header label comes from - our config is 
below with the exception that we changed location / to using proxy_pass

On 05/31/2010 05:29 AM, Timothy Caswell wrote:
> Very strange.  403 errors come from  nginx not node-router.  If you get a 403 I'm pretty sure it's never
hitting the node app. Here is my nginx config for howtonode.org if it helps:
>
> server {
>   listen   80;
>   server_name  www.howtonode.org;
>   rewrite ^/(.*) http://howtonode.org permanent;
> }
>
> upstream backend {
>    server unix:/tmp/howtonode.sock;
> }
>
> server {
>    listen   80;
>    server_name howtonode.org;
>    location / {
>      server_tokens off;

Re: any interest in starting a starting a NYC node meetup? nodeny?

On Mon, May 31, 2010 at 3:34 PM, Marak Squires
<marak.squires@...> wrote:
> I know we have been doing a lot of SSJS talks at NYC.js lately and a
> lot of people haven't been familiar with node and SSJS, or they simply
> aren't able to use node in their current production stack. I really
> hate seeing the browser not get enough attention at our meetings and i
> really dont like seeing node not getting enough attention overall.
>
> I've been talking to a few people in the area and I THINK there is
> enough interest to start up a nodejs nyc meetup group.

I'd rather just keep it a part of the nyc.js meetup. The time is like
66/33% browser/node, which is fine by me. It's not like either side
isn't getting presentation time and I don't think different groups of
people would show up if you had two events.

Re: Connection reset notification?

Thanks, the 'end' event does indeed fire when the connection is
severed...unless the http proxy I use for debugging interferes
(duh!!)

On May 26, 9:44 am, Hugo <hhar...@...> wrote:
> Tried that too, but it never fired:
>
> request.connection.addListener('end',function(){sys.puts('End
> event');});
>
> On May 26, 5:01 am, Scott González <scott.gonza...@...> wrote:
>
>
>
> > Try listening for the end event.
>
> > On Wed, May 26, 2010 at 3:23 AM, Hugo <hhar...@...> wrote:
> > > I am working on an application that implements long-polling for real-
> > > time updates to the client, and I need to know in near real-time when
> > > a client disconnects abruptly by closing the browser for example
> > > (connectionreset).
>
> > > I scoured the discussion board for options, but none that really seems
> > > to work; here's what I have tried
>
> > > request.connection.addListener('close',function(err){sys.puts('Closed.
> > > Error flag '+err);}); //Event only triggers after a long time (several
> > > minutes)
> > > request.connection.addListener('error',function(exception)
> > > {sys.puts('Connectionerror: '+exception);}); //Could not get to

Re: WebSocket Connection Issue

It seems to only work by specifying the IP address (or 127.0.0.1) when
creating the WebSocket obj on the client. If I leave as localhost
nothing gets logged through tcpdump until one of the clients
attempting to connect performs a disconnect, at which point all
hanging clients have the connection established.

Thanks for the tips guys. Most likely something funky with my setup
(relatively new to Linux so I wouldn't doubt it), I'll just use the IP
for now.

Cheers,
Greg

On May 31, 8:23 pm, Guillermo Rauch <rau...@...> wrote:
> I'm pushing most of those changes soon, mscdex.
>
>
>
>
>
> On Mon, May 31, 2010 at 6:36 AM, mscdex <msc...@...> wrote:
> > On May 31, 2:30 am, ghjunior <ghjun...@...> wrote:
> > > Hey guys, this might be something particular to my machine/setup but
> > > have any of you been experiencing issues connecting to WebSocket
> > > servers written in node? I've been trying out a few different
> > > WebSocket modules (Socket.IO-node & node-websocket-server for
> > > instance) and my clients are only able to connect once one of the
> > > clients attempting to connect disconnects.
>
> > Assuming you're using Chrome or Chromium, which versions are you

url.parse query string broken when Prototype loaded

I load prototype.js (the non-browser-specific parts) in node.js and it
works 99% correctly. However, the querystring module depends on
nonportable features of the Array.map function. It breaks thusly:

node> url.parse('http://foo.com/bar?buz=a&wug=b', true).query
{ 'buz=a': 0, 'wug=b': 1 }

should be {'buz': 'a', 'wug': 'b'}

This is node.js 0.1.96 on OSX 10.6

The problem is this code:

QueryString.parseQuery = QueryString.parse = function (qs, sep, eq) {
  return (qs || '')
    .split(sep||"&")
    .map(pieceParser(eq||"="))
    .reduce(mergeParams);
};

...

var pieceParser = function (eq) {
  return function parsePiece (key, val) {
    if (arguments.length !== 2) {
      // key=val, called from the map/reduce
       key = key.split(eq);
      return parsePiece(
        QueryString.unescape(key.shift(), true),
        QueryString.unescape(key.join(eq), true)

Re: any interest in starting a starting a NYC node meetup? nodeny?

"I'd rather just keep it a part of the nyc.js meetup. The time is like
66/33% browser/node, which is fine by me. It's not like either side
isn't getting presentation time and I don't think different groups of
people would show up if you had two events."

You opinion is duly noted, and ignored. I don't care what you think or
what is "fine by you". This is a thread to determine if there are
enough people who are interested in attending a separate node meetup
where we could dive into materials that we will never have the time to
discuss at NYC.js. There's no question that one meeting a month is not
sufficient enough time to adequately cover both topics. Please don't
derail this thread with your personal opinions, just let me know if
you would be willing to attend. I'll take your response as a "no".

-Marak

Re: any interest in starting a starting a NYC node meetup? nodeny?

Wow. That's some way to get people engaged.

On Jun 1, 12:15 am, Marak Squires <marak.squi...@...> wrote:
> "I'd rather just keep it a part of the nyc.js meetup. The time is like
> 66/33% browser/node, which is fine by me. It's not like either side
> isn't getting presentation time and I don't think different groups of
> people would show up if you had two events."
>
> You opinion is duly noted, and ignored. I don't care what you think or
> what is "fine by you". This is a thread to determine if there are
> enough people who are interested in attending a separate node meetup
> where we could dive into materials that we will never have the time to
> discuss at NYC.js. There's no question that one meeting a month is not
> sufficient enough time to adequately cover both topics. Please don't
> derail this thread with your personal opinions, just let me know if
> you would be willing to attend. I'll take your response as a "no".
>
> -Marak

--

-- 
You received this message because you are subscribed to the Google Groups "nodejs" group.
To post to this group, send email to nodejs@...
To unsubscribe from this group, send email to nodejs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.

hola - Repsonse Empty - waa?

Sandboxing Execution

Hey,

I am currently using Tornado as a RPC server which executes user-made
JS code using PyV8. It was easy to sandbox the user's code and kill it
if it runs too long and make sure they don't access anything they
aren't allowed to.

However I was looking at converting it to a Node.js server, but I have
no idea if its even possible to sandbox variables the user's script
would have access to (for example the user trying to require socket
and connecting to things).

Is this possible to accomplish at all?

fs.writeFile regression

The following test program which writes a big utf8 string:

var sys = require('sys');
var fs = require('fs');

function t1() {
  x = 'sdf\u1234dskfj';
  for (var i=0; i<15; i++) x += x;
  fs.writeFile('/tmp/foo', x, function(err) {
      sys.puts('Wrote ' + x.length + ' bytes');
    });
}

t1();

crashes thusly:

buffer:46
      return this.utf8Write(string, offset);
                  ^
TypeError: Offset is out of bounds
    at Buffer.write (buffer:46:19)
    at Object.write (fs:204:14)
    at writeAll (fs:362:6)
    at fs:371:27
    at node.js:204:9

It doesn't crash if you specify 'ascii' encoding. On the fly utf8
encoding in the file io system makes my head hurt.