Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8369435
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 9, 20262026-06-09T13:38:37+00:00 2026-06-09T13:38:37+00:00

I am trying to get a C::A app work in nginx fastcgi environment (debian

  • 0

I am trying to get a C::A app work in nginx fastcgi environment (debian 6.0) and using spawn-fcgi.

C::A route is configured using $self->mode_param( path_info=> 1, param => 'rm' );

the problem is that whatever C::A app urls (example.com/cities, example.com/profile/99 etc ) I am requesting, it always displays the homepage which is what the example.com/index.pl does.

my nginx setup is

server {
    listen   80;
    server_name example.com;
    root /var/www/example.com/htdocs;
    index  index.pl index.html;

    location / {
        try_files $uri $uri/ /index.pl;
    }

    location ~ .*\.pl$ {
            include fastcgi_params;   # this is the stock fastcgi_params file supplied in debian 6.0
            fastcgi_index index.pl;
            fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
            fastcgi_param PERL5LIB "/var/www/example.com/lib";
            fastcgi_param CGIAPP_CONFIG_FILE "/var/www/example.com/conf/my.conf";
            fastcgi_pass unix:/var/run/fcgiwrap.socket;
    }

}

I have successfully setup few php apps in similar fashion.

in this case, however, I suspect that I am not passing essential fastcgi_param down to C::A which is required by it.

what’s your thoughts?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-09T13:38:39+00:00Added an answer on June 9, 2026 at 1:38 pm

    I ended up solving the problem with a workaround in my C::A app. And I am documenting it here.

    So I didn’t managed to have nginx pass along the PATH_INFO down to my C::A app. To work around this, I set the PATH_INFO with the value of REQUEST_URI in my C::A app so it picks up the correct runmode.

    Also, nginx isn’t passing QUERY_STRING either so I had to append $query_string to the catch all route in order to pass along QUERY_STRING down as well.

    my nginx config ends up like this:

    server {
        listen   80;
        server_name example.com;
        root /var/www/example.com/htdocs;
        index  index.pl index.html;
    
        location / {
            try_files $uri $uri/ /index.pl?$query_string;
        }
    
        location ~ .*\.pl$ {
                include fastcgi_params;   # this is the stock fastcgi_params file supplied in debian 6.0
                fastcgi_index index.pl;
                fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
                fastcgi_param PERL5LIB "/var/www/example.com/lib";
                fastcgi_param CGIAPP_CONFIG_FILE "/var/www/example.com/conf/my.conf";
                fastcgi_pass unix:/var/run/fcgiwrap.socket;
        }
    
    }
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I am trying to get my cell app to work using the push registry
I find my self out of ideas trying to get this app to work.
I'm trying to get my local dev django app to work after following these
I'm trying to get a very simple Spring @mvc app to work and I'm
I'm trying to get Spatialite to work with my django app, however, I've hit
I'm trying to get some app info using Apple API, that gives me an
I'm trying to get the django-cms to work on google-app-engine. Did anyone succeed in
I trying to get the tabview app to work, its working fine in the
I've been trying to get a new Django app to work, where I call
I have been trying all day to get app-engine sdk to work nothing has

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.