Issue #1649
The [lazy] `enabled` setting in server.conf is not a valuable setting and should be removed.
Description
There is a configuration option for lazy, 'enabled', that must be set to true or the content WSGI application doesn't redirect. If the content WSGI application always redirected (and this setting didn't exist), the only difference is that the client would get a 302 redirect and then a 404 or 503 if they haven't set up the lazy services. This isn't harmful, and it makes it easier to debug.
Therefore we should remove it before releasing 2.8 and being stuck with a pointless setting.
Associated revisions
Revision 0f100dbb
View on GitHub
Remove the enabled
setting for lazy.
This setting didn't do anything beyond stopping the content WSGI application from redirecting the client. If the lazy services haven't been setup, the client will receive a HTTP 503 or HTTP 404.
closes #1649
History
#1
Updated by jcline@redhat.com almost 5 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to jcline@redhat.com
- Triaged changed from No to Yes
#2
Updated by jcline@redhat.com almost 5 years ago
- Status changed from ASSIGNED to POST
#3
Updated by Anonymous almost 5 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulp|0f100dbb81db860753cc97958bc315bc57eee4bc.
#4
Updated by rbarlow almost 5 years ago
- Platform Release set to 2.8.0
#5
Updated by dkliban@redhat.com almost 5 years ago
- Status changed from MODIFIED to 5
#6
Updated by dkliban@redhat.com almost 5 years ago
- Status changed from 5 to CLOSED - CURRENTRELEASE
#7
Updated by bmbouter almost 2 years ago
- Tags Pulp 2 added
Please register to edit this issue
Remove the
enabled
setting for lazy.This setting didn't do anything beyond stopping the content WSGI application from redirecting the client. If the lazy services haven't been setup, the client will receive a HTTP 503 or HTTP 404.
closes #1649