Re: [1.8 to 1.10] Why I had to set trailing slash to false in my DRF urls.py in order to make things work like before the update

Hi, I think the error message is pretty self explaining. You are using DRF - what are you using for the frontend? Which URLs are being called? By default all django urls should end in a trailing slash - for example : /posts/1/ and if you are calling these from a django template page this is

[1.8 to 1.10] Why I had to set trailing slash to false in my DRF urls.py in order to make things work like before the update

Hi, I was running on 1.8, using django mainly for his API with DRF. Everything worked well. Since I went on with 1.10 I have this kind of message when I make a PUT request to my API : You called this URL via POST, but the URL doesn't end in a slash and you have APPEND_SLASH set. Django