[wildfly-dev] Removing curl support from management HTTP
Darran Lofthouse
darran.lofthouse at jboss.com
Wed Jan 8 09:36:42 EST 2014
On 08/01/14 13:59, Arun Gupta wrote:
> I would agree with Heiko, Curl is often used by admins in their shell
> scripts. This makes their scripts portable.
>
> Is there an overhead to supporting curl ?
Not necessarily, new features are being discussed regarding
authentication at this point I am just trying to confirm if my
perception that users are using tools like curl is actually true ;-)
>
> Arun
>
> On Wed, Jan 8, 2014 at 4:35 AM, Darran Lofthouse
> <darran.lofthouse at jboss.com> wrote:
>> Hello Ladislav,
>>
>> No 'reasoning' as such at this point, and no decisions taken yet. We
>> are currently discussing the future of domain management especially over
>> HTTP and I need to understand how important tools like this are.
>>
>> We originally had support for standard HTTP clients on the requirements
>> list, just need to validate now if it was a valid requirement ;-)
>>
>> Regards,
>> Darran Lofthouse.
>>
>>
>> On 08/01/14 11:58, Ladislav Thon wrote:
>>>> Just starting to plan some upstream changes for WildFly and just wanted
>>>> to gauge how much simple http tools like curl are in use?
>>>>
>>>> If we were to completely disable their use would it cause problems?
>>>
>>> That would be a blocker regression for me :-)
>>>
>>> Could you share what's the reasoning behind this? I use curl basically for everything that supports HTTP interaction (unless I build a specialized tool, but even then, I use curl for debugging the tool. It's immensely useful and I would hate losing it).
>>>
>>> LT
>>>
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
>
>
More information about the wildfly-dev
mailing list