Lightning, I think what Kasper means to say is that there are a few reasons why AWS isn’t authorizing your request, and the likelihood that Django is somehow involved in that error is pretty much zero.
HTTP 403 means that some authorization/permission isn’t sufficient for the server to fulfill the request. Look into your AWS configs or contact their support team. That said, I have no right to speak for Kasper, so my interpretation may, in itself, generate a 403. > On Feb 4, 2021, at 11:36 PM, Kasper Laudrup <[email protected]> wrote: > > On 05/02/2021 06.05, Lightning Bit wrote: >> Does anyone know how to bypass the 403 error on AWS S3 with Django where the >> static files are not allowed to show up on the site? >> > > Ah, yes. The 403 error we all heard of. Everyone knows how to bypass that. > Everyone except you. > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/ff1118ea-b429-3264-5bea-8f8a01f245ef%40stacktrace.dk. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CH2PR14MB39130275C1DDBA94452D89E1C0B29%40CH2PR14MB3913.namprd14.prod.outlook.com.
