Re: [Mongrel] "Client closed socket" spewage

Dan, sorry but I totally forgot that you're on win32. Not a good brain day for me. Let me test this all out tonight and get back to you. I'll post beta gems that you can get from the win32 side too. Zed On 4/21/06 2:25 PM, "Daniel Berger" <[EMAIL PROTECTED]> wrote: > > I'll try the prerelea

Re: [Mongrel] "Client closed socket" spewage

Yeah, beta gems tend to only release for the posix side of things because, ehem, I'm a lazy bastard. I'll do up a better release. I'll get ahold of you soon about cleaning up the win32 side of things so that everything is nice and unified into one simple script. Zed On 4/21/06 7:17 PM, "Luis L

Re: [Mongrel] "Client closed socket" spewage

On 4/21/06, Zed Shaw <[EMAIL PROTECTED]> wrote: > Ah, see what happens when you don't test? Thanks Brian for clueing Dan in. > Dan, let me know how this works. Zed, beta gems are *nix only, right? Thats why the dependencies are broken... Let me know the release schedule and the todo so we could

Re: [Mongrel] "Client closed socket" spewage

Ah, see what happens when you don't test? Thanks Brian for clueing Dan in. Dan, let me know how this works. Zed On 4/21/06 3:13 PM, "Berger, Daniel" <[EMAIL PROTECTED]> wrote: >> -Original Message- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] On Behalf Of Zed Shaw >> Sent: Fr

Re: [Mongrel] "Client closed socket" spewage

On 4/21/06, Bryan Soto <[EMAIL PROTECTED]> wrote: > > I seem to be having some problems: > > > > C:\>gem install mongrel --source=http://mongrel.rubyforge.org/releases/ > > Attempting local installation of 'mongrel' > > Local gem file not found: mongrel*.gem > > Attempting remote installation of 'm

Re: [Mongrel] "Client closed socket" spewage

On 4/21/06, Berger, Daniel <[EMAIL PROTECTED]> wrote: > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of Zed Shaw > > Sent: Friday, April 21, 2006 12:13 PM > > To: mongrel-users@rubyforge.org > > Subject: Re: [Mongrel] "Client closed socket" spewag

Re: [Mongrel] "Client closed socket" spewage

> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Zed Shaw > Sent: Friday, April 21, 2006 12:13 PM > To: mongrel-users@rubyforge.org > Subject: Re: [Mongrel] "Client closed socket" spewage > > Also, there's a pre-release up that dumps more informatio

Re: [Mongrel] "Client closed socket" spewage

On 4/21/06 2:13 PM, "Zed Shaw" <[EMAIL PROTECTED]> wrote: > Another thing is that, if you have your fronting web server configured right > so it deals with the static files, then you should see these for static > files at all. This means that Mongrel is actually serving the file when > really

Re: [Mongrel] "Client closed socket" spewage

Thanks for the reply Zed. However, this is just a local server for development. There's no proxy, no frontend web server for serving static content, and no external client (at least, that I know of). Just me futzing around in IE on localhost to make sure everything looks ok. Running the same

Re: [Mongrel] "Client closed socket" spewage

Hi Dan, I added those reports for people who have crappy proxy servers that keep closing the connections. Lighttpd does this quite frequently for no apparent reason. I'm really starting to not like lighttpd. Basically, if the file is being served to the client and the client closes the connecti

[Mongrel] "Client closed socket" spewage

Hi all, Ruby 1.8.4 Rails 1.1.2 Mongrel 0.3.12 I'm seeing this output from the Mongrel server: Client closed socket requesting file C:/eclipse/workspace/dslscheduler/public/javascripts/prototype.js: Invalid argument It seems to be harmless, but I'm curious as to what's causing it. Any ideas? T