Issue accessing API routes over HTTPS

[mrtimp]

I had an issue where it looked like Laravel was throwing a NotFoundHttpException exception and Dingo was returning a JSON document like:

{
"message": "404 Not Found"
}

When accessing API routes over HTTPS. I took the default code from the Dingo documentation (and excluded the Post route as I didn't have that in my application):

Route::api(['version' => 'v1'], function()
{
Route::get('users', function()
{
return User::all();
});
});

and when I was calling https://myproject/users I was getting the above error.

What is somewhat more confusing is when I reconfigured the route to:

Route::group([ 'version' => 'v1' ], function() {
{
Route::get('users', function()
{
return User::all();
});
});

I didn't get any error. I did some more investigation and I found a similar issue on the Laravel IO forums:

http://laravel.io/forum/03-21-2014-https-definition-in-routesphp

this forum post indicated someone had had similar issues when accessing standard routes over HTTPS. My use case was slightly different as I was using Apache 2.2 rather than Nginx but when I followed their instructions and adjusted the Laravel Illuminate\Routing\Route::httpOnly method I could access my route via Route::api and standard Route::groups.

I'm really not sure if this is a Dingo or a Laravel issue.

Any suggestions would be appreciated.

[jasonlewis]

This should be fixed now within the API itself (1e7b469)

I've made a pull request to fix the underlying bug in Laravel (laravel/framework#4150).

Cheers Tim!