Issue with urlencoded parameter containing + or &

hey, query_string is web standard, you can use it whenever you want. phalcon way is mapping /controller/action/param - but for query string is space too ;) eg ?q=search_word phalcon have got methods to get query string $this->request->get("q");

If you don' need SEO friendly url and need to use query_string then use it.

Second: your router file shouldn't use $_GET['_url'], you can use $_SERVER['REQUEST_URI']

<?php

$router = new Phalcon\Mvc\Router();

$router->setUriSource(\Phalcon\Mvc\Router::URI_SOURCE_SERVER_REQUEST_URI);

$router->removeExtraSlashes(true);
$router->setDefaultController('index');
$router->setDefaultAction('index');

$router->add("/whatever","whatever:index");

return $router;

for example for virtual server for nginx

server {
    listen 80;
    server_name domain.tld www.domain.tld;

    root /home/domain.tld/public;
    index index.php index.html index.htm;

    location ~* \.(eot|otf|ttf|woff)$ {
        add_header Access-Control-Allow-Origin *;
    }

    location = /favicon.ico {
      log_not_found off;
    }

    location / {
            try_files $uri $uri/ /index.php?&$args;
    }

    location ~ \.php$ {
        try_files $uri =404;
            fastcgi_split_path_info ^(.+\.php)(/.+)$;
            fastcgi_pass unix:/var/run/php5-fpm.sock;
            fastcgi_index index.php;
            include fastcgi_params;
    }

    location ~ /\.ht {
            deny all;
    }
}

Thanks for your reply. Perhaps I need to clarify further. I'm aware of the many ways to use the querystring and have done so already, but I consider this a workaround. I'm not using $_GET['_url'], I was just checking it's contents to see if I could discover a point where I could intercept the param before it is wrongly decoded.

In short: I'm trying to find a way to use urlencoded params in a Phalcon route. Perhaps even more bluntly: I think it is a bug that urlencoded params are not relayed properly, but was hoping that I was doing something wrong.

we have similar routes in Album O'Rama:

https://album-o-rama.phalcon.io/album/52/Kid+A https://album-o-rama.phalcon.io/album/20685/Born+To+Die+-+The+Paradise+Edition

The characters '+' are converted to spaces, but you're right, although Phalcon is not converting those characters, I think the browser/web server/php is doing that transformation, no sure why. I'm testing on Windows with Apache and the behavior is the same, maybe this behavior is related to PHP.

Just wanted to comment that I was having the exact same problem (though in my case it was not just for SEO) & the [B] flag fixed it for me too. Thanks for posting the solution.

Might I suggest you amend your original subject to include [solved]?

I am getting Object not found error when i put B flag in project root htaccess file

Can you help me with this?

Thanks for that suggestion. It made me realise that mod_rewrite might be the culprit. I found that if I add the [B] flag to my config, I do receive a urlencoded string as a param.

For background see: https://httpd.apache.org/docs/2.2/mod/mod_rewrite.html#rewriteflags .

This .htaccess works for me:

<IfModule mod_rewrite.c>
   RewriteEngine On
   RewriteCond %{REQUEST_FILENAME} !-d
   RewriteCond %{REQUEST_FILENAME} !-f
   RewriteRule ^(.*)$ index.php?_url=/$1 [QSA,L,B]
</IfModule>