You cannot post messages because only members can post, and you are not currently a member.
Description:
Discussion about Rack development.
|
|
|
Rack 1.1, a modular Ruby webserver interface
|
| |
Hello, Today, with a few days delay, we are proud to announce the release of Rack 1.1. = Rack, a modular Ruby webserver interface Rack provides a minimal, modular and adaptable interface for developing web applications in Ruby. By wrapping HTTP requests and responses in the simplest way possible, it unifies and distills the API for web... more »
|
|
|
Rack with SOAP integration
|
| |
Hi All, I am new to Rack. I am ROR developer. I have to work SOAP webservice integration between a Rack and a Rails application. Rack app should be a soap server and Rails app should be a soap client. How to work on it? Anybody here, please help me. Give some simple sample code to handle soap application between this.... more »
|
|
|
make Rack::Session::Cookie spec pass under 1.9.2dev
|
| |
There appears to be a small change to the Marshal output under 1.9.2dev that makes it output differently than under 1.9.1. Tested with Ruby trunk r26127. --- Otoh, I feel this test is so fragile that it's probably best to scrap it and rely on the round-trip tests... Pushed out to the "mri-1.9.2dev" branch of git://git.bogomips.org/rack... more »
|
|
|
Upcoming 1.1 release
|
| |
Some things left to do: I think we should update Rack::VERSION and Rack.release to 1.1. We shouldn't remove Auth::OpenID without putting it to rack-contrib. Also I updated the README, I hope I forgot nobody in the THANKS.
|
|
|
Should fcgi catch EPIPE?
|
| |
15:17:37 < stbuehler> chris2: hi! i've been told to ask you... i'd like to know how to get rid of the EPIPE backtraces in my fastcgi.crash.log :) 15:17:52 < stbuehler> fastcgi-spec: "When a Web server is not multiplexing requests over a transport connection, the Web server can abort a request by closing the request's transport connection." - so i... more »
|
|
|
Don't munge PATH_INFO in URLMap
|
| |
Make URLMap not squeeze slashes ("/") in PATH_INFO. I'm not sure why this was the original behavior but it makes it impossible to process requests like "[link]" and the like. [link] Thanks, Ryan From 67f7f9b4ee1907b2db0e6addc0ad65 f7d53916f4 Mon Sep 17 00:00:00 2001... more »
|
|
|
Call for 1.1.0 release
|
| |
I'd to cut a 1.1 release before the new year. I'm going to put in the work for the release notes and actual gem push. Now that we are on Gemcutter, the entire rack core team has push access. Heres an overview of the major changes: * Relaxes SPEC to allow subclasses. - This is the major change I want to get out there. Right now Rails... more »
|
|
|
mod_rack hex-unescapes PATH_INFO
|
| |
Hi, I'm tryining Rack under Apache2 mod_rack module (Phusion Passenger). I've realized that Apache2 automatically unescapes hexadecimal symbols in the request URI so they arrive escaped to the Rack application. Most probably this is an appropriate behavior but it breaks my Rack application as I validate the path info specting just ASCII symbols and not... more »
|
|
|
Difficulties with multiple value posts
|
| |
Hi, I've recently had some difficulties getting Rack to handle POST parameters with multiple values properly. I'm (now) aware of the naming conventions used to get multiple values but that doesn't help much when you don't have control over those names (e.g. when they are defined in an API spec)... more »
|
|
|
|
