Cloaking exceptions raised by get_object_or_404().

[Ishwar Bhat]

When we use get_object_or_404() method to query an object, sometimes due to invalid inputs it will through exceptions. Instead can it raise 404 directly?
Ex:

Models:

>>class Test1(models.Model):
>>    c2 = models.CharField(max_length=10)

>>class Test2(models.Model):
>>    c1 = models.UUIDField(primary_key=True, default=uuid.uuid4)
>>    c2 = models.CharField(max_length=10)

query:

1. Below statement raises valueError:

       >> get_object_or_404(Test1, pk='test') 
       >> - invalid literal for int() with base 10: 'test'
   

2. Below statement raises ValidationError:

       >> get_object_or_404(Test2, pk="test")
       >> - 'test' is not a valid UUID.
   

So this method will throw different exceptions in different scenario. So would it be possible to raise 404 exceptions even if it finds invalid values.

[Adwait Thattey]

Yes this behavior exists.

But it seems more appropriate to throw the errors instead of 404.
This seems to be more of a server issue of trying to compare strings with integers rather than an inappropriate client input

[Mariusz Felisiak]

Duplicate of #22303.