URL handling improvements
-------------------------
Key: LS-516
URL: http://dev.sourcefabric.org/browse/LS-516
Project: Liquidsoap
Issue Type: New Feature
Reporter: Samuel Mimram
Assignee: David Baelde
>From the ML:
> 2) checking source URL status
For knowing if it's connected or not we have an internal flag, and I
could easily make it available as a command. However, a quick look at
the code didn't suffice to convince me that this flag still makes
sense -- it doesn't seem to be updated. Moreover, one of the planned
changes to input.http() and others would automatically bring that kind
of feature.
> (or any HTTP error codes 4xx which could give a hint what is going wrong
> like (not found, unauthorized)
> seesection 10.4 Client Error 4xx at
> http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html )
For that, the log file is a natural solution. But I guess it could be
more convenient to have a command indicating the last HTTP answer
code.
Could you please create a new ticket for those two features?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://dev.sourcefabric.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network
management toolset available today. Delivers lowest initial
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Savonet-devl mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-devl
