rack-devel archive mirror (unofficial) https://groups.google.com/group/rack-devel
 help / color / mirror / Atom feed
From: Noah Gibbs <noah_gibbs@yahoo.com>
To: "rack-devel@googlegroups.com" <rack-devel@googlegroups.com>
Subject: Problem with env hash and YARD?
Date: Fri, 3 May 2013 09:54:24 -0700 (PDT)	[thread overview]
Message-ID: <1367600064.8793.YahooMailNeo@web122606.mail.ne1.yahoo.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1200 bytes --]

I'm having an odd problem using YARD with Rack::URLMap and I'm curious if it's a known thing.

I'm mounting the YARD Rack endpoint ("http://rubydoc.info/docs/yard/0.7.4/YARD/Server/RackAdapter") under /yard in my URLmap.  I then go to "/yard/docs".  It's calling the endpoint with a path of "/yard/docs" rather than "/docs" -- but if I mount a proc that calls through to the adapter and check env["PATH_INFO"], it properly and correctly contains "/docs" at that point, not "/yard/docs".

I searched the YARD adapter code, and it seems to be using Rack::Request.new(env).path_info...  Which, of course, check env["PATH_INFO"].  Which should be correct.

But it's not.

Any ideas?  This is weirding me out.

Random other bits:  I'm running under Thin 1.5.1 with Rack 1.5.2 and YARD 0.8.6.1.  YARD is including WEBrick::HTTPUtils, but shouldn't actually be running under WEBrick.

-- 

--- 
You received this message because you are subscribed to the Google Groups "Rack Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rack-devel+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.



[-- Attachment #2: Type: text/html, Size: 3214 bytes --]

                 reply	other threads:[~2013-05-03 17:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://groups.google.com/group/rack-devel

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1367600064.8793.YahooMailNeo@web122606.mail.ne1.yahoo.com \
    --to=rack-devel@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).