Re: CherryPy broken Basic-Auth (for non-ISO-8859-1 strings) - Fix stuck with attempt of a library clean-up

Paul,

I haven't seen you replying @ github, so just to repeat: it's now @ pypi in 
v14.2.0.
Feel free to PR any improvements/bugfixes/test coverage/docs if you feel 
like contributing.

Have a nice day :)

субота, 21 квітня 2018 р. 20:45:28 UTC+2 користувач Sviatoslav Sydorenko 
(@webknjaz) написав:
>
> Hi Paul,
>
>
> I was going to finish that and had it half-done, but got overwhelmed with 
> other stuff and it became out of focus. I have much more than that to do, 
> but my capacity is limited. It's still on my list.
> You can help by submitting PRs against unfinished branch to augment it 
> incrementally: https://github.com/cherrypy/cherrypy/pull/1683
>
>
> Now, what you *can do* in your work project as a completely valid 
> workaround:
>
> Regarding having you own fork: that's not really necessary, because it's a 
> CherryPy tool you refer to and it's completely extendable and replaceable 
> thing.
> All you have to do is to create your own *tool* the same way and then use 
> it instead. You could register your own toolbox or register that tool to 
> *cherrypy.tools* namespace.
> Once upstream is improved you can get back to use the original tool.
>
> Ref: https://docs.cherrypy.org/en/latest/extend.html#tools
>
>
> P.S. Sorry for not getting back to you, sometimes I try to postpone things 
> to get back to them later or they just get lost. Just so you could 
> understand: I currently have 1349 unread github notifications and 
> who-knows-how-many of those from other sources.
> P.P.S. Another thing you could do is to encourage others/yourself to share 
> maintenance of project you clearly depend on: we would be really grateful 
> to anyone trying to reduce our load.
>
>
> Have a nice day and I hope your case will get solved for good!
>
>
> субота, 21 квітня 2018 р. 17:28:56 UTC+2 користувач Paul Jaros написав:
>>
>> Hello
>>
>> I'm using CherryPy @work and found out that there is a problem when a 
>> browser sends their Basic-Auth string encoded in UTF-8. I've documented the 
>> behaviour on Stackoverflow 
>> <https://stackoverflow.com/questions/48009727/cherrypy-allways-decodes-basic-auth-with-iso-8859-1>and 
>> opend a Github Issue <https://github.com/cherrypy/cherrypy/issues/1680>.
>> Everthing felt like we could work out the issue, until it was found there 
>> was a duplicate authentication modul 
>> <https://github.com/cherrypy/cherrypy/issues/1688> which needs some 
>> merging and deprecating first. 
>>
>> After a month of further changes, both efforts have come to a full stop. 
>> Now two addional months later there have been no progress on any of those 
>> two issues.
>>
>> I know this is opensource. I know that, generally speaking, I can create 
>> my own branch and fix it to my liking. I'm willing to provide improvements, 
>> but I have no clue what the master-plan for the de-duplication of the 
>> authentication module is and thus don't know how to help there,
>>
>> I have my supriors asking how/if this issue is progessing and I can't 
>> give them a good answer. Right now I'm considering of switching framework 
>> because I fear that this is issue will never be fixed or that it will 
>> emerge to late to be useful.
>>
>> *My question:*
>> Did I miss anything? Are there any options I've missed? Did anybody had 
>> similar issues?
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups "cherrypy-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cherrypy-users+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/[email protected]
To post to this group, send email to cherrypy-users-/JYPxA39Uh5TLH3MbocFF+G/[email protected]
Visit this group at https://groups.google.com/group/cherrypy-users.
For more options, visit https://groups.google.com/d/optout.