Ticket Details

ngnix rewrites (and possibly other web servers) have a leading forward-slash

BUG Ticket (closed) 

###What happened:
- The asset filter in `config/bootstrap.php` assumes the request url has no leading forward-slash. The proper way to rewrite on some web servers (eg. nginx) adds a leading slash.


###What was expected:
- The request url should be trimmed of leading slashes before splitting the string.

Fix has been committed here: http://rad-dev.org/forks/jlogsdon/li3_docs/commits/view/d1db6579332952d64199c479deffd711c33ef86a
on 04.17.10 reported by: jlogsdon owned by: nate

Updates

on 04.17.10 by jlogsdon
  • title was changed to ngnix rewrites (and possibly other web servers) have a leading forward-slash
				

			


		
			

								
					on 04.18.10				
				
					by jlogsdon				

			
				

					
Maybe "proper" was bad wording, but one of the ways. Besides even that, the fact that core routing works with the trailing slash leads to inconsistent behavior here.
				

			


		
			

				(fixed)				
					on 09.20.10				
				
					by nate				

			
				

					
  • owner was changed to nate
    • 

  • status was changed to closed
    • 

  • resolution was changed to fixed
Committed, thanks for the patch.