Forum: Ruby on Rails Rails startup error in segments.rb

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
Alex S. (Guest)
on 2009-02-02 14:44
(Received via mailing list)
=> Booting WEBrick...
/usr/local/lib/ruby/gems/1.9.1/gems/actionpack-2.2.2/lib/
action_controller/routing/segments.rb:6: warning: encoding option is
ignored - N
=> Rails 2.2.2 application started on http://0.0.0.0:3000
=> Ctrl-C to shutdown server; call with --help for options
[2009-02-02 12:03:54] INFO  WEBrick 1.3.1

Can anyone explain me what exactly it means ? Ruby 1.9.1 on cygwin. On
Ruby 1.8.7 Rails started without this error.
Jeff E. (Guest)
on 2009-02-03 22:50
(Received via mailing list)
Jeff S. (Guest)
on 2009-03-03 20:27
(Received via mailing list)
When I googled the warning, this post was the first thing (and the
second) that came up.  If you've found more info, I'd love to hear it.
Jeff S. (Guest)
on 2009-03-03 20:37
(Received via mailing list)
On Feb 2, 5:16 am, Alex S. <removed_email_address@domain.invalid> wrote:

> 
/usr/local/lib/ruby/gems/1.9.1/gems/actionpack-2.2.2/lib/action_controller/routing/segments.rb:6: 
warning: encoding option is ignored - N

Found by googling segments.rb SAFE_PCHAR patch:
http://rails.lighthouseapp.com/attachments/91693/r...
Conrad T. (Guest)
on 2009-03-03 21:49
(Received via mailing list)
On Mar 3, 2009, at 10:26 AM, Jeff S. <removed_email_address@domain.invalid> 
wrote:

>>> => Booting WEBrick...
>>> /usr/local/lib/ruby/gems/1.9.1/gems/actionpack-2.2.2/lib/
>>> action_controller/routing/segments.rb:6: warning: encoding option is
>>> ignored - N
>>> => Rails 2.2.2 application started onhttp://0.0.0.0:3000
>>> => Ctrl-C to shutdown server; call with --help for options
>>> [2009-02-02 12:03:54] INFO  WEBrick 1.3.1
>>
>>> Can anyone explain me what exactly it means ? Ruby 1.9.1 on
>>> cygwin. On
>>> Ruby 1.8.7 Rails started without this error.

This has been fixed in Edge Rails.

Good luck,

-Conrad
This topic is locked and can not be replied to.