Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

REMOTE_ADDR is not specified in the spec.

  • Loading branch information...
commit daf1469b3c445ffa37896b37d915b4e0c3dc2de6 1 parent b401396
@miyagawa miyagawa authored
Showing with 1 addition and 1 deletion.
  1. +1 −1  PSGI/FAQ.pod
2  PSGI/FAQ.pod
@@ -338,7 +338,7 @@ objects should be passed and which method they need to implement,
there will be so much duplicated code in the backends, some of
which may be buggy.
-For instance, PSGI defines C<< $env->{REMOTE_ADDR} >> as a
+For instance, PSGI defines C<< $env->{SERVER_NAME} >> as a
nihen added a note

$env->{SERVER_NAME} can't be a instance of Net::IP is clearly.
I think when deleted "For instance" paragraph is good.
This topic should be written only for the env hash.
Because, fact, $env->{'psgi.input'} is object.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
string. What if the PSGI spec required it to be an instance of Net::IP?
Backend code would have to depend on the Net::IP module, or have to
write a mock object that implements ALL of Net::IP's methods.
Please sign in to comment.
Something went wrong with that request. Please try again.