Rufen Sie die Webseite https://dl.example.com/ auf und melden Sie sich mit
-+Ihrem Benutzernamen und Passwort an. Nach der Anmeldung erscheint die folgende
-+Seite:
-+
-+
-+
Klicken Sie, wie in der Abbildung gezeigt, auf "Durchsuchen" und wählen Sie
-+die zu sendende Datei aus.
-+
Klicken Sie auf "Senden" und warten Sie, bis die Datei hochgeladen wurde,
-+siehe folgende Abbildung.
-+
-+
-+
-+
Klicken Sie auf "Per E-Mail verschicken", um den Link zur gerade
-+hochgeladenen Datei einem beliebigen Empfänger über Ihr E-Mail Programm zu
-+schicken.
-+
-+
Bei Verwendung der Standardeinstellungen hat der Empfänger eine Woche Zeit, um
-+die Datei herunterzuladen, bevor diese automatisch gelöscht wird. Diese Frist
-+kann jedoch geändert werden indem Sie die entsprechenden Parameter vor dem
-+hochladen anpassen.
-+
Durch einen Klick auf "Aktive Tickets" am unteren Ende der Seite, kann die
-+Liste der hochgeladenen Dateien eingesehen und einzelne Tickets verwaltet
-+werden.
Rufen Sie die Webseite https://dl.example.com/ auf und melden Sie sich mit
-+Ihrem Benutzernamen und Passwort an. Nach der Anmeldung erscheint die folgende
-+Seite:
-+
-+
-+
Klicken Sie auf "Neue Upload-Erlaubnis" am unteren Ende der Seite
-+
-+
-+
-+
Geben Sie Ihre E-Mailadresse an.
-+
Klicken Sie auf "Erstellen" um die Erlaubnis zu erstellen.
-+
-+
-+
-+
Klicken Sie auf "Per E-Mail verschicken", um die Upload-Erlaubnis an einen
-+beliebigen Empfänger zu schicken.
-+
-+
Der Empfänger braucht nach Erhalt der Upload-Erlaubnis den darin enthaltenen
-+Link lediglich in einem Browser aufzurufen und die Anweisungen am Bildschirm zu
-+befolgen. Sobald der Empfänger die Datei hochgeladen hat, wird Ihnen eine
-+Bestätigungs-E-Mail mit einem Link zur hochgeladenen Datei zugeschickt.
Vor dem Versand einer Datei ist es möglich die Verfallsfristen unter dem Abschnitt "Weitere Optionen" anzupassen.
-+
-+
Wenn Sie möchten, dass die Datei nicht automatisch gelöscht wird, aktivieren
-+Sie die Option "Ticket ohne Verfallsfrist ", die Sie unter "Weitere Optionen"
-+finden. Die Datei wird dann solange zur Verfügung stehen, bis sie manuell
-+gelöscht wird.
-+
Wenn Sie für jeden einzelnen Download einer Datei eine Meldung erhalten
-+möchten, geben Sie Ihre E-Mail-Adresse im Feld "Bei Download folgende
-+E-Mailadresse benachrichtigen" ein. Sie finden das Feld unter "Weitere
-+Optionen".
-+
Frist in # Tagen:
-+
-+Hier können Sie die maximale Anzahl von Tagen angeben, welche die gesendete
-+Datei auf dem Server erhalten bleibt. Nach Ablauf dieser Frist wird die Datei
-+automatisch gelöscht, unabhängig davon ob sie heruntergeladen wurde oder
-+nicht.
-+
Frist in # Stunden, nach dem letzten Download:
-+
-+
Hier können Sie die maximale Anzahl von Stunden angeben, für welche die Datei
-+nach dem letzten Download noch auf dem Server verbleiben soll. Jeder weiterer
-+Download legt die Verfallsfrist um die angegebene Stundenanzahl erneut fest.
-+Ist die Frist abgelaufen, wird die Datei automatisch gelöscht.
-+
Diese Frist-Angabe ermöglicht Ihnen bei Verwendung von großen Zeiträumen
-+(Tage/Wochen) häufig verwendete Tickets für einen unbestimmten Zeitraum aktiv
-+zu erhalten und sie automatisch zu löschen, sobald sie nicht mehr verwendet
-+werden.
-+
Wird die Frist-Angabe hingegen mit kurzen Zeiträumen verwendet (bis zu 24
-+Stunden), wird das Ticket nach dem Herunterladen schnell entfernt, gibt dem
-+Empfänger aber noch einen kleinen Spielraum für weitere Downloads.
-+
-+
Frist in # Downloads:
-+
-+Hier können Sie festlegen, wie oft eine Datei insgesamt vom Server
-+heruntergeladen werden kann. Bei Erreichen dieser Anzahl wird die Datei
-+automatisch gelöscht.
-+
Wird mindestens eine der oben beschriebenen Fristen überschritten, verfällt das
-+Ticket und wird somit automatisch gelöscht. Sie können eine oder mehrere
-+Fristen deaktivieren, indem Sie den entsprechenden Parameter auf "0" setzen.
Click on the button under "Upload File" (labelled either "Browse" or "Choose
-+File") as outlined in the picture and pick the file you need to send.
-+
Click "Upload", and wait until the file is uploaded as shown:
-+
-+
-+
-+
Click "Send via E-Mail" to send an e-mail to someone, containing the link
-+to the file you just uploaded.
-+
-+
By default, the recipient has one week to download the file before it is
-+automatically cleaned up. You can change this behavior by setting some
-+parameters before uploading.
-+
You can see a list of files you have uploaded and manage them by clicking on
-+the "List active tickets" button, at the bottom of the page.
Click on the "New grant" link at the bottom of the page to start a new
-+grant:
-+
-+
-+
-+
Enter your email address.
-+
Click "Create" to generate an upload grant:
-+
-+
-+
-+
Click "Send via E-Mail" to send an e-mail to someone, containing the link
-+that will allow him to send you any file.
-+
-+
Your recipient simply needs to follow the instructions contained in the link
-+itself. Once he uploads the file into the server, you will receive an email
-+containing another link to the file just uploaded.
Before uploading a file, you can customize how the download and cleanup is
-+performed by setting some "Advanced" parameters:
-+
-+
-+
If you want your file to never be deleted please check the "Permanent
-+ticket" checkbox. Your file will always be available until you manually
-+remove it.
-+
If you want to be notified every time someone downloads the file you can
-+write your e-mail in the "Get notified by email" box. You'll receive
-+notifications every time the file is successfully downloaded or removed from
-+the server. This is great if you want extra confirmation that your email has
-+been acted upon.
-+
-+
Expire in total # of hours:
-+
-+Type the maximal number of hours the uploaded file is allowed to be kept on
-+the server. After this period is passed the file will be deleted from the
-+server whether is was downloaded or not.
-+
Expire in # of hours after last dl:
-+
-+
Type the number of hours the uploaded file is allowed to be kept on the
-+server after being downloaded. Another download will extend the lifetime of
-+the ticket for the specified number of hours. After this period is passed
-+without activity, the file is be deleted from the server.
-+
This feature, when used with a long period (days or weeks), allows "hot"
-+tickets to be kept alive only until used, and be deleted automatically
-+afterward.
-+
When used with a short period (24 hours or less), allows to remove the ticket
-+as soon as being downloaded, allowing the recipient some margin to download
-+the file more than once.
-+
-+
Expire after # of downloads:
-+
-+Type the number of times the uploaded file is allowed to be downloaded in
-+total. After this amount is reached the file will be deleted from the
-+server. Handy if you need to ensure the file is downloaded just once from a
-+single person.
-+
If at least one of these parameters expires the file will be deleted. You can
-+set any parameter to "0" to disable the condition.
Primero, diríjase a https://dl.example.com/ y autentíquese usando su usuario y
-+contraseña.
-+
Esta página debería ser mostrada:
-+
-+
-+
Cliquee en el botón bajo "Subir fichero" (llamado "Examinar" or "Escoja
-+fichero") como se ve en la imagen y seleccione el fichero que necesita subir.
-+
Click en "Subir" y espere mientras el fichero es subido como aquí se muestra:
-+
-+
-+
-+
Click en "Enviar vía e-mail" para enviar un e-mail a alguien con el enlace
-+al fichero que acaba de subir.
-+
-+
Por defecto, el receptor tiene una semana para descargar el fichero antes de
-+este sea eliminado automáticamente. Puede cambiar este comportamiento
-+configurando algunos parámetros antes de la subida.
-+
Puede ver una lista de ficheros que ha subido y administrarlos cliqueando en el
-+botón "Listar tickets activos" a pie de página.
Primero, diríjase a https://dl.example.com/ y autentíquese usando su usuario y
-+contraseña.
-+
Esta página debería ser mostrada:
-+
-+
-+
Click en el enlace "Nueva concesión" al pie de página para empezar una nueva
-+concesión:
-+
-+
-+
-+
Introduzca su dirección de e-mail.
-+
Click en "Crear" para generar una concesión de subida:
-+
-+
-+
-+
Click en "Enviar vía E-Mail" para enviar un e-mail a alguien con el enlace
-+a quién le permitirá subir un fichero para usted.
-+
-+
El receptor simplemente necesitará seguir las instrucciones contenidas en el
-+propio enlace. Una vez este suba un fichero al servidor, usted recibirá un
-+e-mail que contendrá un enlace a el fichero que ha sido subido.
Antes de subir un fichero, puede personalizar cómo se realizará su descarga y
-+su limpieza configurando algunos parámetros "avanzados":
-+
-+
-+
Si quiere que su fichero nunca sea eliminado, por favor, marque la casilla
-+"Ticket permanente". Su fichero estará disponible hasta que usted lo elimine
-+manualmente.
-+
Si quiere ser notificado cada vez que alguien descargue el fichero puede
-+escribir una dirección de e-mail en el campo "Notificar vía e-mail". Recibirá
-+notificaciones cada vez que el fichero sea correctamente descargado o
-+eliminado del servidor. Esto es genial si desea una confirmación extra de que
-+su e-mail actúa en consecuencia.
-+
-+
Expirar en un total de # horas:
-+
-+Introduzca el número máximo de horas que a un fichero subido le está
-+permitido permanecer en el servidor. Pasado este período el fichero será
-+eliminado del servidor independientemente de si fue descargado o no.
-+
Expirar en # horas tras la última descarga:
-+
-+
Introduzca el número de horas que a un fichero subido se le permite
-+permanecer en el servidor tras haber sido descargado. Una nueva descarga
-+alargará el tiempo de vida del ticket durante el número de horas
-+especificado. Pasado este período sin actividad el fichero será eliminado del
-+servidor.
-+
Esta funcionalidad, cuando es usada con un largo período (días o semanas),
-+permite a los "hot" tickets permanecer vivos mientras están en uso y ser
-+elimindos automáticamente cuando ya no son demandados.
-+
Cuando es usado en un período corto (24 horas o menos), permite eliminar el
-+ticket tan pronto como sea descargado, permitiendo al receptor algo de margen
-+para descargar el fichero más de una vez.
-+
-+
Expirar tras # descargas:
-+
-+Introduce el número total de veces que es permitido descargar un fichero
-+subido. Alcanzado este número el fichero será eliminado del servidor. Útil si
-+quiere asegurarse de que el fichero es descargado sólo una vez por una sola
-+persona.
-+
Si al menos uno de estos parámetros expira el fichero será eliminado. Puede
-+configurar cualquier parámetro a "0" para deshabilitar la condición.
Tout d'abord, allez sur https://dl.example.com/ et authentifier vous avec votre
-+nom d'utilisateur et votre mot de passe.
-+
Vous devriez voir la page ci-dessous:
-+
-+
-+
Sélectionnez le fichier à envoyer avec le bouton "Parcourir"
-+
Cliquer sur le bouton "Télécharger" pour envoyer votre fichier.
-+
-+
-+
-+
Cliquez sur le bouton "Envoyer par e-mail" pour envoyer par e-mail le lien
-+contenant le fichier que vous venez de télécharger.
-+
-+
Par défaut, le destinataire dispose d'une semaine pour télécharger le fichier
-+avant qu'il ne soit automatiquement supprimé. Vous pouvez modifier ce
-+comportement en définissant certains paramètres avant de le télécharger.
-+
Vous pouvez voir la liste des fichiers que vous avez téléchargés et aussi les
-+gérer en cliquant sur "Tickets actifs", au bas de la page.
Tout d'abord, allez sur https://dl.example.com/ et authentifier vous avec votre
-+nom d'utilisateur et votre mot de passe.
-+
Vous devriez voir la page ci-dessous:
-+
-+
-+
Cliquez sur "Nouvelle concession" au bas de la page :
-+
-+
-+
-+
Entrer votre adresse email.
-+
Cliquez sur "Créer" pour générer une concession:
-+
-+
-+
-+
Cliquez sur "Envoyer par e-mail" pour envoyer par e-mail le lien qui
-+permettra de vous faire parvenir un fichier.
-+
-+
Le destinataire devra simplement suivre les instructions contenues dans le
-+mail. Une fois, le fichier téléchargé sur le serveur, vous recevrez un e-mail
-+contenant un autre lien vers le fichier que vous pourrez télécharger.
Avant de télécharger un fichier, vous pouvez personnaliser les paramètres de
-+téléchargement et de supression en modifiant les "Paramètres avancés":
-+
-+
-+
Si vous souhaitez que votre fichier ne soit jamais supprimé cocher "Ticket
-+permanent/téléchargement". Ceci rendra votre fichier toujours disponible
-+jusqu'à ce que vous le retiriez manuellement.
-+
Si vous voulez être averti chaque fois que quelqu'un télécharge le fichier,
-+vous pouvez renseigner votre adresse e-mail dans le champs "Notifier par
-+e-mail". Vous recevrez une notification chaque fois que le fichier sera
-+téléchargé avec succès ou retiré du serveur.
-+
-+
Expirera dans # jours:
-+
-+Indiquer le nombre de jours maximal durant lesquels ce fichier pourra être
-+téléchargé. Passé ce délai ce fichier ne pourra plus être téléchargé et sera
-+automatiquement supprimé.
-+
Expirera dans # heures après le dernier téléchargement:
-+
-+Indiquer le nombre d'heures pendant lesquelles ce fichier restera disponible
-+après avoir été téléchargé. Si celui-ci n'est pas téléchargé pendant le délai
-+indiqué, il sera automatiquement supprimé.
-+
Expirera après # téléchargement:
-+
-+Indiquer le nombre total de téléchargements autorisé pour ce fichier. Au-delà
-+de cette limite, ce fichier sera automatiquement supprimé.
-+
Si au moins un de ces paramètres est appliqué le fichier sera supprimé. Mettre
-+n'importe quel paramètre à "0" pour désactiver son état.
Collegarsi al sito https://dl.example.com/ ed autenticarsi col proprio nome
-+utente e password.
-+
La schermata iniziale si presenta come segue:
-+
-+
-+
Cliccare su "Sfoglia", come indicato nell'immagine e selezionare il file
-+desiderato da inviare.
-+
Cliccare su "Invia" ed attendere fino al completamento dell'operazione,
-+indicata dalla seguente schermata:
-+
-+
-+
-+
Cliccare su "Invia per e-mail" per inviare il collegamento al file appena
-+caricato via e-mail ad un qualsiasi destinatario usando il proprio programma
-+di posta elettronica.
-+
-+
Con le impostazioni predefinite, il destinatario avrà una settimana di tempo
-+per scaricare il file prima che venga eliminato automaticamente. È possibile
-+cambiare la scadenza impostando alcuni parametri prima dell'invio del file.
-+
La lista dei file caricati è gestibile cliccando sul collegamento "Ticket
-+attivi", disponibile in basso alla pagina.
Collegarsi al sito https://dl.example.com/ ed autenticarsi col proprio nome
-+utente e password.
-+
La schermata iniziale si presenta come segue:
-+
-+
-+
Cliccare su "Nuova concessione", in basso alla pagina.
-+
-+
-+
-+
Inserire il proprio indirizzo e-mail.
-+
Cliccare su "Crea" per generare la concessione.
-+
-+
-+
-+
Cliccare su "Invia per email" per inviare la concessione e le istruzioni di
-+utilizzo tramite e-mail ad un qualsiasi destinatario.
-+
-+
Il destinatario, una volta ricevuto il collegamento alla concessione, dovrà
-+semplicemente seguire le indicazioni. Quando il destinatario avrà terminato
-+l'invio del file, riceverete immediatamente (tramite e-mail) conferma ed un
-+collegamento al file appena trasferito.
Prima di procedere all'invio di un file, è possibile impostare la sua
-+scadenza accedendo ai parametri avanzati:
-+
-+
-+
Se desiderate che il file non venga mai eliminato, abilitare l'opzione
-+"Nessuna scadenza", disponibile nel pannello "Avanzate".
-+
Se desiderate ricevere notifica per ogni singolo scaricamento, inserite il
-+vostro indirizzo e-mail nella casella "Notifica via e-mail", disponibile nel
-+pannello avanzate.
-+
-+
Scadenza in # giorni:
-+
-+Inserire il numero massimo di giorni che il file inviato verrà mantenuto nel
-+server. Passato il termine, il file viene eliminato automaticamente, sia che
-+venga scaricato o meno.
-+
Scadenza in # ore dopo l'ultimo scaricamento:
-+
-+
Inserire il numero ore che il file inviato verrà mantenuto nel server dopo
-+essere stato scaricato. Ogni scaricamento estende il termine del numero di
-+ore specificato. Passato il termine, il file viene eliminato automaticamente.
-+
Questa funzionalità, usata insieme ad un lungo periodo (giorni o settimane),
-+permette di mantenere ticket molto utilizzati attivi per un periodo
-+indefinito, e rimuoverli automaticamente alla cessazione di utilizzo.
-+
Usata invece con periodi brevi (24 ore o meno), consente di eliminare il
-+ticket rapidamente dopo lo scaricamento, dando al destinatario del margine
-+per effettuarne altri.
-+
-+
Scadenza in # scaricamenti
-+
-+Inserire il numero di volte che il file può venire scaricato in totale dal
-+server. Passato il termine, il file viene eliminato automaticamente.
-+
La scadenza del ticket viene effettuata alla scadenza di uno qualsiasi dei
-+termini impostati (solitamente del termine che arriva prima). È possibile
-+impostare un parametro a "0" per disabilitarne il relativo termine.
Ga alleereerst naar https://dl.example.com/ en log in met uw gebruikersnaam en
-+wachtwoord.
-+
U ziet nu onderstaande pagina:
-+
-+
-+
Klik op de knop "Bestand kiezen" (of "Browse") onder "Een bestand uploaden"
-+zoals aangegeven op bovenstaand figuur. Selecteer vervolgens het bestand
-+dat u wilt versturen.
-+
Klik op "Bestand uploaden" en wacht totdat het bestand is geüpload. Als het
-+uploaden is gelukt verschijnt de volgende figuur:
-+
-+
-+
-+
Klik "Verstuurd per e-mail" om de e-mail naar de gewenste persoon te
-+versturen. Deze mail bevat de link naar het bestand dat u zojuist heeft
-+geüpload.
-+
-+
Standaard heeft de ontvanger één week de tijd om het bestand te downloaden
-+voordat dit bestand automatisch verwijderd wordt. U kunt dit gedrag wijzigen
-+door een aantal parameters in te stellen voordat u het bestand upload.
-+
U kunt een lijst van bestanden die u heeft geüpload zien en wijzigen door op
-+"Actieve tickets" onderaan de pagina te klikken.
Ga alleereerst naar https://dl.example.com/ en log in met uw gebruikersnaam en
-+wachtwoord.
-+
U ziet nu onderstaande pagina:
-+
-+
-+
Klik op de "Nieuwe toekenning" link onderaan de pagina om een nieuwe
-+toekenning te maken.
-+
-+
-+
-+
Vul uw eigen e-mail adres in.
-+
Klik op "Maak" om een upload toekenning te maken.
-+
-+
-+
-+
Klik op "Verstuurd per e-mail" om een e-mail naar iemand te versturen. Deze
-+e-mail bevat een link die het de ontvanger mogelijk maakt om u een groot
-+bestand terug te sturen.
-+
-+
Uw ontvanger hoeft alleen maar de instructies te volgen zoals aangegeven in de
-+mail. Als de ontvanger van de link zijn bestand heeft geüpload naar de server
-+ontvangt u een notificatie e-mail met daarin een link naar het geüploade
-+bestand.
Voordat u een bestand upload kunt u met geavancceerde parameters instellen hoe
-+vaak het bestand gedownload kan worden en of en wanneer het bestand automatisch
-+wordt verwijderd.
-+
-+
-+
Als u niet wilt dat uw bestand ooit automatisch wordt verwijderd zet dan
-+een vinkje bij "Ticket permanent maken". Uw bestand zal altijd beschikbaar
-+blijven totdat u het bestand zelf handmatig verwijderd.
-+
Als u iedere keer als iemand uw bestand download een melding wilt ontvangen
-+vul dan uw e-mail adres in bij "Ontvang een e-mail notificatie nadat het
-+bestand is gedownload". U ontvangt nu iedere keer een melding als uw bestand
-+succesvol is gedownload of wanneer het automatisch van de server is
-+verwijderd. Deze functie is erg handig als u er zeker van wilt zijn dat men
-+gereageerd heeft op de door u verstuurde e-mail.
-+
-+
Vervalt na # dagen:
-+
-+Vul hier het maximaal aantal dagen in dat een geüpload bestand op de server
-+blijft staan. Na deze periode wordt het bestand automatisch van de server
-+verwijderd. Het maakt hierbij niet uit of het bestand wel of niet
-+gedownload was tijdens het ingestelde tijdsinterval.
-+
Vervalt na # dagen na de laatste download:
-+
-+
Vul hier het maximaal aantal dagen in dat een geüpload bestand op de server
-+blijft staan nadat het gedownload is. Een volgende download zorgt ervoor
-+dat de teller weer wordt gereset. Nadat het ingestelde aantal dagen is
-+verstreken zonder dat er een download van het bestand heeft plaatsgevonden,
-+zal het bestand automatisch van de server verwijderd worden.
-+
Deze functie zorgt ervoor dat populaire bestanden bewaard blijven maar
-+nadat deze is gezakt automatisch verwijderd worden. Het is aan
-+te raden om het tijdsinterval in te stellen op meerdere dagen of weken.
-+
Zorg er altijd voor dat u het tijdsinterval zodanig instelt dat een
-+ontvanger van uw e-mail het bestand indien nodig twee keer kan downloaden.
-+
-+
Vervalt na # downloads:
-+
-+Vul het aantal keer in dat het geüploade bestand gedownload kan worden. Als
-+het ingestelde aantal downloads bereikt is zal het bestand automatisch van
-+de server verwijderd worden. Deze functie is handig als u er bijvoorbeeld
-+zeker van wilt zijn dat uw bestand één keer gedownload wordt door één
-+persoon.
-+
Als één van bovenstaande ingestelde parameters verloopt dan zal het bestand
-+verwijderd worden. Als u "0" invult bij een parameter dan zal deze
-+uitgeschakeld worden.
Rufen Sie die Webseite https://dl.example.com/ auf und melden Sie sich mit
--Ihrem Benutzernamen und Passwort an. Nach der Anmeldung erscheint die folgende
--Seite:
--
--
--
Klicken Sie, wie in der Abbildung gezeigt, auf "Durchsuchen" und wählen Sie
--die zu sendende Datei aus.
--
Klicken Sie auf "Senden" und warten Sie, bis die Datei hochgeladen wurde,
--siehe folgende Abbildung.
--
--
--
--
Klicken Sie auf "Per E-Mail verschicken", um den Link zur gerade
--hochgeladenen Datei einem beliebigen Empfänger über Ihr E-Mail Programm zu
--schicken.
--
--
Bei Verwendung der Standardeinstellungen hat der Empfänger eine Woche Zeit, um
--die Datei herunterzuladen, bevor diese automatisch gelöscht wird. Diese Frist
--kann jedoch geändert werden indem Sie die entsprechenden Parameter vor dem
--hochladen anpassen.
--
Durch einen Klick auf "Aktive Tickets" am unteren Ende der Seite, kann die
--Liste der hochgeladenen Dateien eingesehen und einzelne Tickets verwaltet
--werden.
Rufen Sie die Webseite https://dl.example.com/ auf und melden Sie sich mit
--Ihrem Benutzernamen und Passwort an. Nach der Anmeldung erscheint die folgende
--Seite:
--
--
--
Klicken Sie auf "Neue Upload-Erlaubnis" am unteren Ende der Seite
--
--
--
--
Geben Sie Ihre E-Mailadresse an.
--
Klicken Sie auf "Erstellen" um die Erlaubnis zu erstellen.
--
--
--
--
Klicken Sie auf "Per E-Mail verschicken", um die Upload-Erlaubnis an einen
--beliebigen Empfänger zu schicken.
--
--
Der Empfänger braucht nach Erhalt der Upload-Erlaubnis den darin enthaltenen
--Link lediglich in einem Browser aufzurufen und die Anweisungen am Bildschirm zu
--befolgen. Sobald der Empfänger die Datei hochgeladen hat, wird Ihnen eine
--Bestätigungs-E-Mail mit einem Link zur hochgeladenen Datei zugeschickt.
Vor dem Versand einer Datei ist es möglich die Verfallsfristen unter dem Abschnitt "Weitere Optionen" anzupassen.
--
--
Wenn Sie möchten, dass die Datei nicht automatisch gelöscht wird, aktivieren
--Sie die Option "Ticket ohne Verfallsfrist ", die Sie unter "Weitere Optionen"
--finden. Die Datei wird dann solange zur Verfügung stehen, bis sie manuell
--gelöscht wird.
--
Wenn Sie für jeden einzelnen Download einer Datei eine Meldung erhalten
--möchten, geben Sie Ihre E-Mail-Adresse im Feld "Bei Download folgende
--E-Mailadresse benachrichtigen" ein. Sie finden das Feld unter "Weitere
--Optionen".
--
Frist in # Tagen:
--
--Hier können Sie die maximale Anzahl von Tagen angeben, welche die gesendete
--Datei auf dem Server erhalten bleibt. Nach Ablauf dieser Frist wird die Datei
--automatisch gelöscht, unabhängig davon ob sie heruntergeladen wurde oder
--nicht.
--
Frist in # Stunden, nach dem letzten Download:
--
--
Hier können Sie die maximale Anzahl von Stunden angeben, für welche die Datei
--nach dem letzten Download noch auf dem Server verbleiben soll. Jeder weiterer
--Download legt die Verfallsfrist um die angegebene Stundenanzahl erneut fest.
--Ist die Frist abgelaufen, wird die Datei automatisch gelöscht.
--
Diese Frist-Angabe ermöglicht Ihnen bei Verwendung von großen Zeiträumen
--(Tage/Wochen) häufig verwendete Tickets für einen unbestimmten Zeitraum aktiv
--zu erhalten und sie automatisch zu löschen, sobald sie nicht mehr verwendet
--werden.
--
Wird die Frist-Angabe hingegen mit kurzen Zeiträumen verwendet (bis zu 24
--Stunden), wird das Ticket nach dem Herunterladen schnell entfernt, gibt dem
--Empfänger aber noch einen kleinen Spielraum für weitere Downloads.
--
--
Frist in # Downloads:
--
--Hier können Sie festlegen, wie oft eine Datei insgesamt vom Server
--heruntergeladen werden kann. Bei Erreichen dieser Anzahl wird die Datei
--automatisch gelöscht.
--
Wird mindestens eine der oben beschriebenen Fristen überschritten, verfällt das
--Ticket und wird somit automatisch gelöscht. Sie können eine oder mehrere
--Fristen deaktivieren, indem Sie den entsprechenden Parameter auf "0" setzen.
Click on the button under "Upload File" (labelled either "Browse" or "Choose
--File") as outlined in the picture and pick the file you need to send.
--
Click "Upload", and wait until the file is uploaded as shown:
--
--
--
--
Click "Send via E-Mail" to send an e-mail to someone, containing the link
--to the file you just uploaded.
--
--
By default, the recipient has one week to download the file before it is
--automatically cleaned up. You can change this behavior by setting some
--parameters before uploading.
--
You can see a list of files you have uploaded and manage them by clicking on
--the "List active tickets" button, at the bottom of the page.
Click on the "New grant" link at the bottom of the page to start a new
--grant:
--
--
--
--
Enter your email address.
--
Click "Create" to generate an upload grant:
--
--
--
--
Click "Send via E-Mail" to send an e-mail to someone, containing the link
--that will allow him to send you any file.
--
--
Your recipient simply needs to follow the instructions contained in the link
--itself. Once he uploads the file into the server, you will receive an email
--containing another link to the file just uploaded.
Before uploading a file, you can customize how the download and cleanup is
--performed by setting some "Advanced" parameters:
--
--
--
If you want your file to never be deleted please check the "Permanent
--ticket" checkbox. Your file will always be available until you manually
--remove it.
--
If you want to be notified every time someone downloads the file you can
--write your e-mail in the "Get notified by email" box. You'll receive
--notifications every time the file is successfully downloaded or removed from
--the server. This is great if you want extra confirmation that your email has
--been acted upon.
--
--
Expire in total # of hours:
--
--Type the maximal number of hours the uploaded file is allowed to be kept on
--the server. After this period is passed the file will be deleted from the
--server whether is was downloaded or not.
--
Expire in # of hours after last dl:
--
--
Type the number of hours the uploaded file is allowed to be kept on the
--server after being downloaded. Another download will extend the lifetime of
--the ticket for the specified number of hours. After this period is passed
--without activity, the file is be deleted from the server.
--
This feature, when used with a long period (days or weeks), allows "hot"
--tickets to be kept alive only until used, and be deleted automatically
--afterward.
--
When used with a short period (24 hours or less), allows to remove the ticket
--as soon as being downloaded, allowing the recipient some margin to download
--the file more than once.
--
--
Expire after # of downloads:
--
--Type the number of times the uploaded file is allowed to be downloaded in
--total. After this amount is reached the file will be deleted from the
--server. Handy if you need to ensure the file is downloaded just once from a
--single person.
--
If at least one of these parameters expires the file will be deleted. You can
--set any parameter to "0" to disable the condition.
Primero, diríjase a https://dl.example.com/ y autentíquese usando su usuario y
--contraseña.
--
Esta página debería ser mostrada:
--
--
--
Cliquee en el botón bajo "Subir fichero" (llamado "Examinar" or "Escoja
--fichero") como se ve en la imagen y seleccione el fichero que necesita subir.
--
Click en "Subir" y espere mientras el fichero es subido como aquí se muestra:
--
--
--
--
Click en "Enviar vía e-mail" para enviar un e-mail a alguien con el enlace
--al fichero que acaba de subir.
--
--
Por defecto, el receptor tiene una semana para descargar el fichero antes de
--este sea eliminado automáticamente. Puede cambiar este comportamiento
--configurando algunos parámetros antes de la subida.
--
Puede ver una lista de ficheros que ha subido y administrarlos cliqueando en el
--botón "Listar tickets activos" a pie de página.
Primero, diríjase a https://dl.example.com/ y autentíquese usando su usuario y
--contraseña.
--
Esta página debería ser mostrada:
--
--
--
Click en el enlace "Nueva concesión" al pie de página para empezar una nueva
--concesión:
--
--
--
--
Introduzca su dirección de e-mail.
--
Click en "Crear" para generar una concesión de subida:
--
--
--
--
Click en "Enviar vía E-Mail" para enviar un e-mail a alguien con el enlace
--a quién le permitirá subir un fichero para usted.
--
--
El receptor simplemente necesitará seguir las instrucciones contenidas en el
--propio enlace. Una vez este suba un fichero al servidor, usted recibirá un
--e-mail que contendrá un enlace a el fichero que ha sido subido.
Antes de subir un fichero, puede personalizar cómo se realizará su descarga y
--su limpieza configurando algunos parámetros "avanzados":
--
--
--
Si quiere que su fichero nunca sea eliminado, por favor, marque la casilla
--"Ticket permanente". Su fichero estará disponible hasta que usted lo elimine
--manualmente.
--
Si quiere ser notificado cada vez que alguien descargue el fichero puede
--escribir una dirección de e-mail en el campo "Notificar vía e-mail". Recibirá
--notificaciones cada vez que el fichero sea correctamente descargado o
--eliminado del servidor. Esto es genial si desea una confirmación extra de que
--su e-mail actúa en consecuencia.
--
--
Expirar en un total de # horas:
--
--Introduzca el número máximo de horas que a un fichero subido le está
--permitido permanecer en el servidor. Pasado este período el fichero será
--eliminado del servidor independientemente de si fue descargado o no.
--
Expirar en # horas tras la última descarga:
--
--
Introduzca el número de horas que a un fichero subido se le permite
--permanecer en el servidor tras haber sido descargado. Una nueva descarga
--alargará el tiempo de vida del ticket durante el número de horas
--especificado. Pasado este período sin actividad el fichero será eliminado del
--servidor.
--
Esta funcionalidad, cuando es usada con un largo período (días o semanas),
--permite a los "hot" tickets permanecer vivos mientras están en uso y ser
--elimindos automáticamente cuando ya no son demandados.
--
Cuando es usado en un período corto (24 horas o menos), permite eliminar el
--ticket tan pronto como sea descargado, permitiendo al receptor algo de margen
--para descargar el fichero más de una vez.
--
--
Expirar tras # descargas:
--
--Introduce el número total de veces que es permitido descargar un fichero
--subido. Alcanzado este número el fichero será eliminado del servidor. Útil si
--quiere asegurarse de que el fichero es descargado sólo una vez por una sola
--persona.
--
Si al menos uno de estos parámetros expira el fichero será eliminado. Puede
--configurar cualquier parámetro a "0" para deshabilitar la condición.
Tout d'abord, allez sur https://dl.example.com/ et authentifier vous avec votre
--nom d'utilisateur et votre mot de passe.
--
Vous devriez voir la page ci-dessous:
--
--
--
Sélectionnez le fichier à envoyer avec le bouton "Parcourir"
--
Cliquer sur le bouton "Télécharger" pour envoyer votre fichier.
--
--
--
--
Cliquez sur le bouton "Envoyer par e-mail" pour envoyer par e-mail le lien
--contenant le fichier que vous venez de télécharger.
--
--
Par défaut, le destinataire dispose d'une semaine pour télécharger le fichier
--avant qu'il ne soit automatiquement supprimé. Vous pouvez modifier ce
--comportement en définissant certains paramètres avant de le télécharger.
--
Vous pouvez voir la liste des fichiers que vous avez téléchargés et aussi les
--gérer en cliquant sur "Tickets actifs", au bas de la page.
Tout d'abord, allez sur https://dl.example.com/ et authentifier vous avec votre
--nom d'utilisateur et votre mot de passe.
--
Vous devriez voir la page ci-dessous:
--
--
--
Cliquez sur "Nouvelle concession" au bas de la page :
--
--
--
--
Entrer votre adresse email.
--
Cliquez sur "Créer" pour générer une concession:
--
--
--
--
Cliquez sur "Envoyer par e-mail" pour envoyer par e-mail le lien qui
--permettra de vous faire parvenir un fichier.
--
--
Le destinataire devra simplement suivre les instructions contenues dans le
--mail. Une fois, le fichier téléchargé sur le serveur, vous recevrez un e-mail
--contenant un autre lien vers le fichier que vous pourrez télécharger.
Avant de télécharger un fichier, vous pouvez personnaliser les paramètres de
--téléchargement et de supression en modifiant les "Paramètres avancés":
--
--
--
Si vous souhaitez que votre fichier ne soit jamais supprimé cocher "Ticket
--permanent/téléchargement". Ceci rendra votre fichier toujours disponible
--jusqu'à ce que vous le retiriez manuellement.
--
Si vous voulez être averti chaque fois que quelqu'un télécharge le fichier,
--vous pouvez renseigner votre adresse e-mail dans le champs "Notifier par
--e-mail". Vous recevrez une notification chaque fois que le fichier sera
--téléchargé avec succès ou retiré du serveur.
--
--
Expirera dans # jours:
--
--Indiquer le nombre de jours maximal durant lesquels ce fichier pourra être
--téléchargé. Passé ce délai ce fichier ne pourra plus être téléchargé et sera
--automatiquement supprimé.
--
Expirera dans # heures après le dernier téléchargement:
--
--Indiquer le nombre d'heures pendant lesquelles ce fichier restera disponible
--après avoir été téléchargé. Si celui-ci n'est pas téléchargé pendant le délai
--indiqué, il sera automatiquement supprimé.
--
Expirera après # téléchargement:
--
--Indiquer le nombre total de téléchargements autorisé pour ce fichier. Au-delà
--de cette limite, ce fichier sera automatiquement supprimé.
--
Si au moins un de ces paramètres est appliqué le fichier sera supprimé. Mettre
--n'importe quel paramètre à "0" pour désactiver son état.
Collegarsi al sito https://dl.example.com/ ed autenticarsi col proprio nome
--utente e password.
--
La schermata iniziale si presenta come segue:
--
--
--
Cliccare su "Sfoglia", come indicato nell'immagine e selezionare il file
--desiderato da inviare.
--
Cliccare su "Invia" ed attendere fino al completamento dell'operazione,
--indicata dalla seguente schermata:
--
--
--
--
Cliccare su "Invia per e-mail" per inviare il collegamento al file appena
--caricato via e-mail ad un qualsiasi destinatario usando il proprio programma
--di posta elettronica.
--
--
Con le impostazioni predefinite, il destinatario avrà una settimana di tempo
--per scaricare il file prima che venga eliminato automaticamente. È possibile
--cambiare la scadenza impostando alcuni parametri prima dell'invio del file.
--
La lista dei file caricati è gestibile cliccando sul collegamento "Ticket
--attivi", disponibile in basso alla pagina.
Collegarsi al sito https://dl.example.com/ ed autenticarsi col proprio nome
--utente e password.
--
La schermata iniziale si presenta come segue:
--
--
--
Cliccare su "Nuova concessione", in basso alla pagina.
--
--
--
--
Inserire il proprio indirizzo e-mail.
--
Cliccare su "Crea" per generare la concessione.
--
--
--
--
Cliccare su "Invia per email" per inviare la concessione e le istruzioni di
--utilizzo tramite e-mail ad un qualsiasi destinatario.
--
--
Il destinatario, una volta ricevuto il collegamento alla concessione, dovrà
--semplicemente seguire le indicazioni. Quando il destinatario avrà terminato
--l'invio del file, riceverete immediatamente (tramite e-mail) conferma ed un
--collegamento al file appena trasferito.
Prima di procedere all'invio di un file, è possibile impostare la sua
--scadenza accedendo ai parametri avanzati:
--
--
--
Se desiderate che il file non venga mai eliminato, abilitare l'opzione
--"Nessuna scadenza", disponibile nel pannello "Avanzate".
--
Se desiderate ricevere notifica per ogni singolo scaricamento, inserite il
--vostro indirizzo e-mail nella casella "Notifica via e-mail", disponibile nel
--pannello avanzate.
--
--
Scadenza in # giorni:
--
--Inserire il numero massimo di giorni che il file inviato verrà mantenuto nel
--server. Passato il termine, il file viene eliminato automaticamente, sia che
--venga scaricato o meno.
--
Scadenza in # ore dopo l'ultimo scaricamento:
--
--
Inserire il numero ore che il file inviato verrà mantenuto nel server dopo
--essere stato scaricato. Ogni scaricamento estende il termine del numero di
--ore specificato. Passato il termine, il file viene eliminato automaticamente.
--
Questa funzionalità, usata insieme ad un lungo periodo (giorni o settimane),
--permette di mantenere ticket molto utilizzati attivi per un periodo
--indefinito, e rimuoverli automaticamente alla cessazione di utilizzo.
--
Usata invece con periodi brevi (24 ore o meno), consente di eliminare il
--ticket rapidamente dopo lo scaricamento, dando al destinatario del margine
--per effettuarne altri.
--
--
Scadenza in # scaricamenti
--
--Inserire il numero di volte che il file può venire scaricato in totale dal
--server. Passato il termine, il file viene eliminato automaticamente.
--
La scadenza del ticket viene effettuata alla scadenza di uno qualsiasi dei
--termini impostati (solitamente del termine che arriva prima). È possibile
--impostare un parametro a "0" per disabilitarne il relativo termine.
Ga alleereerst naar https://dl.example.com/ en log in met uw gebruikersnaam en
--wachtwoord.
--
U ziet nu onderstaande pagina:
--
--
--
Klik op de knop "Bestand kiezen" (of "Browse") onder "Een bestand uploaden"
--zoals aangegeven op bovenstaand figuur. Selecteer vervolgens het bestand
--dat u wilt versturen.
--
Klik op "Bestand uploaden" en wacht totdat het bestand is geüpload. Als het
--uploaden is gelukt verschijnt de volgende figuur:
--
--
--
--
Klik "Verstuurd per e-mail" om de e-mail naar de gewenste persoon te
--versturen. Deze mail bevat de link naar het bestand dat u zojuist heeft
--geüpload.
--
--
Standaard heeft de ontvanger één week de tijd om het bestand te downloaden
--voordat dit bestand automatisch verwijderd wordt. U kunt dit gedrag wijzigen
--door een aantal parameters in te stellen voordat u het bestand upload.
--
U kunt een lijst van bestanden die u heeft geüpload zien en wijzigen door op
--"Actieve tickets" onderaan de pagina te klikken.
Ga alleereerst naar https://dl.example.com/ en log in met uw gebruikersnaam en
--wachtwoord.
--
U ziet nu onderstaande pagina:
--
--
--
Klik op de "Nieuwe toekenning" link onderaan de pagina om een nieuwe
--toekenning te maken.
--
--
--
--
Vul uw eigen e-mail adres in.
--
Klik op "Maak" om een upload toekenning te maken.
--
--
--
--
Klik op "Verstuurd per e-mail" om een e-mail naar iemand te versturen. Deze
--e-mail bevat een link die het de ontvanger mogelijk maakt om u een groot
--bestand terug te sturen.
--
--
Uw ontvanger hoeft alleen maar de instructies te volgen zoals aangegeven in de
--mail. Als de ontvanger van de link zijn bestand heeft geüpload naar de server
--ontvangt u een notificatie e-mail met daarin een link naar het geüploade
--bestand.
Voordat u een bestand upload kunt u met geavancceerde parameters instellen hoe
--vaak het bestand gedownload kan worden en of en wanneer het bestand automatisch
--wordt verwijderd.
--
--
--
Als u niet wilt dat uw bestand ooit automatisch wordt verwijderd zet dan
--een vinkje bij "Ticket permanent maken". Uw bestand zal altijd beschikbaar
--blijven totdat u het bestand zelf handmatig verwijderd.
--
Als u iedere keer als iemand uw bestand download een melding wilt ontvangen
--vul dan uw e-mail adres in bij "Ontvang een e-mail notificatie nadat het
--bestand is gedownload". U ontvangt nu iedere keer een melding als uw bestand
--succesvol is gedownload of wanneer het automatisch van de server is
--verwijderd. Deze functie is erg handig als u er zeker van wilt zijn dat men
--gereageerd heeft op de door u verstuurde e-mail.
--
--
Vervalt na # dagen:
--
--Vul hier het maximaal aantal dagen in dat een geüpload bestand op de server
--blijft staan. Na deze periode wordt het bestand automatisch van de server
--verwijderd. Het maakt hierbij niet uit of het bestand wel of niet
--gedownload was tijdens het ingestelde tijdsinterval.
--
Vervalt na # dagen na de laatste download:
--
--
Vul hier het maximaal aantal dagen in dat een geüpload bestand op de server
--blijft staan nadat het gedownload is. Een volgende download zorgt ervoor
--dat de teller weer wordt gereset. Nadat het ingestelde aantal dagen is
--verstreken zonder dat er een download van het bestand heeft plaatsgevonden,
--zal het bestand automatisch van de server verwijderd worden.
--
Deze functie zorgt ervoor dat populaire bestanden bewaard blijven maar
--nadat deze is gezakt automatisch verwijderd worden. Het is aan
--te raden om het tijdsinterval in te stellen op meerdere dagen of weken.
--
Zorg er altijd voor dat u het tijdsinterval zodanig instelt dat een
--ontvanger van uw e-mail het bestand indien nodig twee keer kan downloaden.
--
--
Vervalt na # downloads:
--
--Vul het aantal keer in dat het geüploade bestand gedownload kan worden. Als
--het ingestelde aantal downloads bereikt is zal het bestand automatisch van
--de server verwijderd worden. Deze functie is handig als u er bijvoorbeeld
--zeker van wilt zijn dat uw bestand één keer gedownload wordt door één
--persoon.
--
Als één van bovenstaande ingestelde parameters verloopt dan zal het bestand
--verwijderd worden. Als u "0" invult bij een parameter dan zal deze
--uitgeschakeld worden.
Fix upgrade script and incompatibilities when using MySQL.
--Thanks to Daniel Berteaud.
--
--
--
--
dl 0.18: 2017-09-04
--
Major new features:
--
--
Support for multiple file uploads in both tickets and grants. When multiple
--files are attached, a Zip archive is automatically created with the contents.
--The PHP "Zip" extension is now required.
--
Grants are now reusable. With the new defaults, senders are no longer
--restricted to a single use/file per grant, but can keep reusing the same link
--as needed. The grant, just like a ticket, is then automatically expired when
--left unused for a certain amount of time.
--
Tickets generated while using a grant are now split into a separated
--"Received files" page. The "All tickets" page reserved to administrators
--still shows all tickets combined and color-coded.
--
A new Android client is now available: PokéDL.
--
--
Enhancements:
--
--
The ticket and grant expiration parameters have been streamlined for common
--usage patterns, becoming mostly self-explanatory.
--
When using a grant, the user can now attach a comment alongside the uploaded
--file/s. The comment is sent back to the grant owner in the notification.
--
Tickets now show the generating grant ID in the edit/detailed view.
--
The grant comment assigned during creation is now shown in both the tooltip
--of the grant list and in email notifications involving grant usage.
--
Ticket/grant passwords were previously always included in notifications. The
--password sending policy can now be controlled at creation time, and defaults
--to sending the password only when automatically generated.
--
The subject prefix in email notifications can now be customized.
--
dl-wx now allows to generate grants.
--
General dl-cli overhaul:
--
dl-cli now runs under both python 3 and python 2.7, preferring python 3
--
The password can be read from an external command using passcmd
--
Public-key pinning is now supported through the fingerprint option
--
Multiple files can now be uploaded in a single ticket (for efficiency,
--dl-cli generates a Zip archive locally before uploading)
--
When generating a grant, the email address is now optional if available
--in the configuration file
--
The ConfigObj module is now required
--
--
--
--
Bug fixes:
--
--
Tickets generated while using a grant were incorrectly calculating the expiry
--from the grant creation time, resulting in premature expiration. Ticket
--expiry is now calculated starting at actual upload time.
--
Download of files larger than 2GB would previously fail when using DL with
--MySQL or Postgres. Fix by Daniel Berteaud.
--
Ticket and grant invalid access or invalid password attempts are now logged.
--
Left-clicking on the dl-wx tray's icon on Linux now works as expected.
--
--
Other changes:
--
--
The minimum required PHP version has been raised to 5.5 or higher.
--
Important PHP settings are now preset in the bundled htdocs/.htaccess
--file for the Apache/mod_php combination.
--
Simplified Chinese translation by Guangyu Dong.
--
Russian translation by Олейник О.В.
--
The Thunderbird add-on has been updated to support Thunderbird 52.
--
The Windows dl-wx executable has been rebuilt with SNI support.
--
--
Please note: DL 0.18 requires a database schema update! Please read the
--database upgrade procedure in the README!
--
--
--
dl 0.17.1: 2016-05-01
--
--
Filenames are now sanitized more aggressively when received. This avoids
--browser/client failures when receiving files that contain illegal characters
--for the current platform (which might be legal in another).
--
Filenames containing multibyte characters could previously result in
--unexpected truncation; they're now handled correctly.
--
The uploaded filename is included in grant notifications.
--
The Thunderbird add-on has been updated to support Thunderbird 45.
--
In the ticket details, the full timestamp of the download is now shown.
--
Minor code and documentation fixes.
--
--
--
--
dl 0.17: 2015-06-26
--
--
Login attempts are now logged.
--
Log messages are now more uniform, always including the remote address and
--username (when available).
--
The Thunderbird add-on has been updated to support Thunderbird 38.
--
--
--
--
dl 0.16: 2015-01-22
--
--
The database connection is automatically re-established when timed out after
--slow uploads/downloads (affects systems not using sqlite).
--
dl-cli can now prompt for a password when left unspecified in the
--~/.dl.rc configuration file.
--
Added Japanese translation by Teruo IWAI.
--
Dutch user-guide translation by Maarten Schoonman.
--
--
--
--
dl 0.15: 2014-11-28
--
--
File names with special and/or UTF-8 characters are now correctly preserved
--on all browsers.
--
Added Dutch translation by Maarten Schoonman.
--
--
--
--
dl 0.14: 2014-10-16
--
--
Fixed broken Content-Length header with the Apache/mod_php/mod_deflate
--combination, which would prevent downloads to be resumed.
--
The built-in skin has been updated.
--
The skin can now be customized and set in the configuration file.
--
A work-around has been found to allow PHP 5.4-5.5 to upload files up to 4GB
--(note that starting with PHP 5.6 there is no upload size limitation).
--
Logging of server-side errors has been improved.
--
--
--
--
dl 0.13: 2014-07-31
--
--
The "Active tickets/grants" pages for administrators now show only their own
--tickets, like for normal users. Other tickets are visible in the new "All
--tickets/grants" pages.
--
Upload progress information is now implemented client-side using HTML5/JS,
--which is both more responsive and waives any PHP configuration/version
--restrictions.
--
Ticket/grant/user listings can now be sorted by clicking on the table header.
--
The date/time format can now be customized.
--
Spaces in uploaded file names are now correctly preserved.
--
The REST interface can now be used with the built-in authentication method
--without additional configuration also when using apache/fcgi.
--
The REST interface now supports a method to generate grants.
--
The Thunderbird add-on now includes a new menu command (under "Tools") and a
--new toolbar icon in the composer window to generate and insert grants in the
--current message.
--
Added Brazilian Portuguese and Czech localizations (thanks to Guilherme
--Benkenstein and Jan Štětina).
--
Minor bug/cosmetic fixes.
--
--
DL 0.12 is the last release offering an upgrade path from DL 0.3. Version 0.13
--can only upgrade from 0.4 and above. If you have an old installation, you'll
--need to perform a two step upgrade using an earlier release.
--
--
--
dl 0.12: 2013-12-10
--
--
Add a new configurable "e-mail" address in the preferences, which is used as
--a default when creating grants and receiving notifications.
--
Support for MySQL and PostgreSQL.
--
Support for provided e-mail address with external authentication using
--USER_EMAIL header (useful for LemonLDAP::NG/webSSO).
--
Fix REST interface when used in combination with LemonLDAP::NG/webSSO.
--
Improved French localization.
--
The timezone of the web interface is now customizable.
--
Minor bug/cosmetic fixes.
--
--
Please note: DL 0.12 requires a database schema update! Please read the
--database upgrade procedure in the README!
--
--
--
dl 0.11: 2013-07-05
--
--
Fixed CSRF vulnerability of the admin interface (discovered by Dirk Reimers).
--
Mitigations against session fixation attacks (discovered by Dirk Reimers).
--
Fixed CSRF vulnerability of the REST interface when used in combination with
--HTTP/external authentication.
--
Improved client-side validation of the forms (with HTML5/JS where available).
--
Password hashing for the user/ticket/grant DB switched to PHPass.
--
Progress bar updating improvements.
--
Thunderbird integration is now available through the new included extension
--"Thunderbird-Filelink-DL", which converts attachments to links automatically.
--
Minor bug/cosmetic fixes.
--
--
Please note: DL 0.11 requires a database schema update! Please read the
--database upgrade procedure in the README!
--
Upgrading to DL 0.11 has implication for existing users. The new hashing scheme
--limits usernames to 60 characters and passwords to 72 to prevent DoS attacks.
--Users having usernames/passwords exceeding these limits won't be able to login
--after the upgrade, and can only be managed manually through the command line.
--
The password hash of existing users is automatically rehashed using the new
--scheme upon a successful login (no password change is required).
--
The optional password of tickets and grants is similarly affected and upgraded
--transparently upon successful usage. Tickets/grants having passwords longer
--than 72 characters though will require a manual password reset.
--
To fully prevent CSRF attacks on the REST interface when used in combination
--with HTTP authentication the protocol has been broken. Clients (such as the
--supplied "dl-wx") require an upgrade, though new clients can still communicate
--to an old server.
--
--
--
dl 0.10.1: 2012-03-09
--
--
A bug was fixed in the initialization code that could cause grant uploads to
--fail in certain configurations.
--
--
--
--
dl 0.10: 2012-02-06
--
--
The default configuration file has been renamed to "config.php.dist" and must
--now be manually copied/renamed to be used. If a suitable "config.php" is not
--found in the include/ directory, then the configuration is read from
--"/etc/dl.php". This will allow smoother release upgrades in the future.
--
Notifications of tickets and grants now use the same locale that was used
--during the creation of the ticket/grant itself.
--
A new "Preferences" page has been added, allowing users to change their
--password (currently supported only for internal authentication).
--
Changing "hours after last download" while editing a ticket didn't actually
--extend the ticket lifetime. Changing the ticket lifetime now works correctly.
--
"hours after last download" has been changed to "days after last download".
--
Default ticket/grant expiration settings have been increased significantly.
--
A new REST API has been implemented, allowing external applications to use the
--service programmatically.
--
Two python clients have been added to the distribution: a command-line python
--client "dl-cli" and a graphical client "dl-wx".
--
Minor bug and UI fixes.
--
--
Please note: DL 0.10 requires a database schema and webserver configuration
--update! Please read the database upgrade procedure in the README and the
--relevant notes about web server configuration.
--
--
--
dl 0.9.1: 2011-12-31
--
--
Fixed a grave security issue: unauthorized parties can perform login as any
--arbitrary user when using the built-in authentication mechanism by supplying
--an authorization header. DL versions down to 0.3 are affected.
--
--
--
--
dl 0.9: 2011-04-06
--
--
The settings of tickets and grants are now stored independently.
--
Default ticket/grant settings can be specified in the config file.
--
Most ticket and grant options are now moved into an "advanced" panel.
--
Grant notifications now include the ticket password in the message.
--
Form validation is now also performed in JavaScript.
--
Enlarged the width of the interface to 800px.
--
Users management is now available through the web interface.
--
French, Italian, Spanish and German translation.
--
Multi-line comments can be attached to tickets and grants.
--
Improved the e-mail notification text.
--
Improved ticket and grant listings.
--
Tickets can now be edited after being created.
--
Minor bug and UI fixes.
--
--
--
--
dl 0.8: 2010-07-10
--
--
Update PHP-Gettext to 1.1.10 (fixing several PHP Notices).
--
Fix browser language autodetection (typo, thanks to Bert-Jan Kamp).
--
Fix ticket expiration when using sqlite3 (table locking issues).
--
Do not purge tickets prematurely after an unsuccessful download.
--
Purge tickets immediately after the download, when possible.
--
"useradmin.php" now allows to reset/change user role and password.
--
All notifications are now sent using the default locale.
--
Ticket expiration can be performed with an external utility.
--
The user-guide is now included in the admin interface.
--
--
--
--
dl 0.7: 2010-03-10
--
--
Fix XSS vulnerability for unknown ticket IDs (discovered by Sven Eric Neuz)
--
--
--
--
dl 0.6: 2010-03-03
--
--
Remember the selected language with a cookie.
--
Allow to tune the DB expiration process to improve the performance.
--
Fixed E-Mail subject encoding.
--
German translation update.
--
PHP 5.3 warning fixes.
--
--
--
--
dl 0.5: 2010-02-09
--
--
Fix upload progress-bar on Chrome and Safari.
--
Minor bug, UI and usability fixes.
--
Internationalization support.
--
Italian and German translation.
--
License changed to GNU GPL 2.
--
--
--
--
dl 0.4: 2009-11-24
--
--
Ticket activity can be logged to syslog or a file.
--
The minimal required PHP version is now 5.0.
--
PDO is now used for the users/tickets database (defaulting to a sqlite
--database). Upgrading instructions in the README.
--
The submission form now allows to automatically send a link of the ticket to
--the specified address/es.
--
A ticket can now require a password to be downloaded.
--
"Upload grants" can now be created, allowing others to send you a single file
--through DL.
--
Progress-bar indicator during uploads.
--
Required fields are highlighted when missing.
--
--
--
--
dl 0.3: 2009-09-02
--
--
CSS-ification, with new skin from Kim Thostrup <kim@thostrup.dk>.
"dl" is a simple file sharing service for quick/one-off file transfers. Upload
--a file to get a link you can share. Or create a sharing link to receive files
--from others. The uploaded files are automatically removed when left unused,
--requiring zero additional maintenance.
--
"dl" is built for your users: easy to use with any browser, integrates
--smoothly with Thunderbird for large attachments, works on Android, Windows
--and OSX or straight from the command line for maximum convenience.
Copy the htdocs directory contained in the archive to a directory of
--choice under your web server.
--
--
Copy include/config.php.dist to either include/config.php or
--/etc/dl.php and customize as needed. This usually means changing the URL
--and E-Mail of the service.
--
--
Ensure the include and style/*/include directories are not directly
--accessible externally. Type http://dl.example.com/include/config.php and
--verify that you correctly get an "Access Denied" error.
--
If you use Apache, the provided .htaccess files should be already
--sufficient; consult your web server documentation otherwise.
--
--
Create a spool directory that will be used by the service to store the files,
--user and ticket information. This directory should be outside of the
--document root of your web server. Fix the permissions so that PHP has
--read/write access to it.
--
In the provided include/config.php this is configured as
--/var/spool/dl. If you web server runs as "nobody:nogroup", issue:
DL needs a database to store the ticket and user information. By default, DL
--will use an embedded "sqlite" database stored within the spool directory, but
--some manual setup is still required.
--
To create the database, you need the sqlite3 command.
--On Ubuntu/Debian, sqlite3 can by installed by executing:
--
--sudo apt-get install sqlite3
--
--
You should then execute the provided SQL batch for SQLite with the same user
--as your web server (by using su or sudo if necessary):
If you want to change the database path, or use a real database server, you
--need to properly configure the $dsn parameters in include/config.php
--according to your setup. The DSN string changes according to the PDO module
--that you want to use. Please see one of:
for the most popular configuration choices. When a username/password is
--required, using the appropriate variables $dbUser/$dbPassword is
--preferred instead of embedding the values in the DSN string.
--
The directory include/scripts/db/ provides SQL initialization scripts for
--SQLite, MySQL and PostgreSQL.
The following parameters are required to be set in your php.ini:
--
--
date.timezone: must be set to your system preference.
--
session.auto_start: must be "Off".
--
--
The maximal upload limit is determined by several PHP configuration parameters.
--Check your php.ini for:
--
--
upload_max_filesize: change as needed.
--
post_max_size: must be at least 1M larger than upload_max_filesize.
--
session.gc_maxlifetime: must be long enough to allow large uploads to finish.
--
--
All the above settings can be configured per-directory and affect only DL. In
--addition, the following parameters need to be set for the entire PHP server:
--
--
file_uploads: must be "On".
--
upload_tmp_dir: ensure enough space is available for temporary files.
--
max_file_uploads: change as needed.
--
--
The upload limit as shown in the submission form is determined automatically
--from the upload_max_filesize parameter.
--
Any upload beyond post_max_size will be completely ignored: users will get
--a blank page instead of an error message. You should raise post_max_size
--above upload_max_filesize to get an acceptable "error window" in old
--browsers or browsers with JavaScript disabled.
--
session.gc_maxlifetime (which is in seconds) needs to be long enough for
--your users to complete a large upload. Uploading 500MB on a slow ADSL
--connection can take as much as 12 hours, so set it to at least 43200.
--
If PHP was built as an Apache module you can set per-directory parameters
--through .htaccess (see
--http://www.php.net/manual/en/configuration.changes.php) or directly inside your
--Apache's configuration (see Apache/mod_php for an example). The provided
--htdocs/.htaccess contains a reasonable pre-set, but requires
--AllowOverride All to be set for the directory in your main configuration.
DL can use both an internal and an external user database, by trusting the
--authentication credentials provided by your web server.
--
dl supports both "normal" users and "administrators". A normal user can only
--see and manage tickets created by himself. Administrators can see/manage all
--the tickets.
Once dl has been installed and PHP is set-up correctly, you have to create at
--least one user to be able to log in. User management is handled through the
--command line by using the bundled useradmin.php utility.
--
On the server, execute the following commands with the same user as your web
--server (by using su or sudo if necessary):
--
--cd /your-installation-directory/include/scripts
--php useradmin.php add "admin" "true" "change me"
--
--
where:
--
--
admin is the user name
--
true (or false) sets the administrator status
--
change me is the password
--
--
Repeat as many times as necessary. You should now be able to use the web
--service. Other users/administrators can be added through the web interface.
External authentication should be the preferred form of authentication for
--corporate use since it supports whatever authentication scheme your web server
--already supports (for example, LDAP, ActiveDirectory, etc).
--
To enable external authentication you have to protect the two files:
--
--
admin.php
--
rest.php
--
--
using a "Basic" authentication scheme. You should then set $authRealm to
--the same authentication realm used in your web server. The other files must
--not be protected.
--
DL will implicitly trust the credentials provided by the web server. All users
--are logged in as "normal" by default. The only setup required is adding the
--administrators with useradmin.php without using any password.
--
Logout with HTTP authentication is not guaranteed to work: users should simply
--close their browser to clear their session (closing a tab or window is not
--enough in many browsers). Currently, logout works as expected on:
--
--
Firefox
--
Safari
--
Google Chrome/Chromium
--
--
Logout does not work on:
--
--
Internet Explorer 7/8.
--
Opera 9/10.
--
--
Again, only the Basic authentication is supported, which transmits the
--password in clear-text unless you use SSL.
--
When using external authentication, the HTTP header USER_EMAIL can
--additionally provide the user's default email address. Such header is provided
--automatically, for example, when using "LemonLDAP::NG".
Large file support (for uploads larger than 2GB) requires a combination of PHP
--version, web server and browser support.
--
Apache 2.2 and above support large request bodies but needs to be built for
--64bit (see LimitRequestBody). Same for Lighttpd 1.4 (>2gb but only for
--64bit builds, see server.max-request-size).
--
Due to several bugs in PHP prior to 5.6, upload_max_filesize and
--post_max_size are limited to a 31/32bit integer, which limits the upload
--size to 2/4GB even on 64bit systems. The maximal uploadable sizes are shown
--below:
--
--
--
--
--
--
--
PHP Version
--
Upload limit
--
--
--
--
<5.4
--
2gb: post_max_size = 2147483647
--
--
5.4-5.5
--
4gb: post_max_size = 4294967295
--
--
>=5.6
--
no limit
--
--
--
--
Note that PHP versions before 5.5 are no longer supported, and older versions
--are shown here for reference purposes only.
--
Finally, not all browsers support large file uploads:
--<Directory /your-installation-directory>
-- # Normal DL configuration
-- AcceptPathInfo On
-- AllowOverride Limit
-- Options -Indexes
-- DirectoryIndex index.php index.html
--
-- # Require a Basic authentication scheme for admin/rest.php
-- <FilesMatch "^(admin|rest)\.php$">
-- # The scheme must be Basic
-- AuthType Basic
-- AuthName "Restricted Area"
-- Require valid-user
-- Satisfy any
--
-- # You'll need to provide a valid source for passwords using either the
-- # following or some other authentication source (such as LDAP)
-- AuthBasicProvider file
-- AuthUserFile /path/to/passwd/file
-- </FilesMatch>
--</Directory>
--
--
With LDAP or ActiveDirectory authentication:
--
--<Directory /your-installation-directory>
-- # Normal DL configuration
-- AcceptPathInfo On
-- AllowOverride Limit
-- Options -Indexes
-- DirectoryIndex index.php index.html
--
-- # Require a Basic authentication scheme for admin/rest.php
-- <FilesMatch "^(admin|rest)\.php$">
-- # The scheme must be Basic
-- AuthType Basic
-- AuthName "Restricted Area"
-- Require valid-user
-- Satisfy any
--
-- # Use the LDAP provider (just an example query)
-- AuthBasicProvider ldap
-- AuthzLDAPAuthoritative off
-- AuthLDAPURL ldap://XXXXXX:XXXX/ou=XXXX,dc=XXXX,dc=XXX?sAMAccountName?sub?(objectClass=*)
-- AuthLDAPBindDN "cn=XXXX,ou=XXXXX,dc=XXX,dc=XXX"
-- AuthLDAPBindPassword "XXXXX"
-- </FilesMatch>
--</Directory>
--
FastCGI support in Apache up to 2.2.x is severely lacking with all the
--available modules: mod_fcgi, mod_fcgid (now merged officially into
--Apache's mod_fcgi) and mod_fastcgi.
--
--
mod_fcgi and mod_fcgid buffer the entire request in memory before
--handing-off the request to PHP, meaning that the maximal upload limit is
--bound to your available memory at the time of the request, independently of
--how PHP is setup. This is a known, old bug that's still present in both
--mod_fcgi 2.2.14 and mod_fcgid 2.3.4. There is no known work-around:
--either use mod_php or use a different server.
--
mod_fastcgi has been proved to be slow (and sometimes unstable) in most
--configurations. It is not advisable to use PHP with mod_fastcgi.
--
--
For the REST service to work, independently of the authentication method,
--mod_rewrite needs to be enabled and configured as follows:
--
--<Directory /your-installation-directory>
-- # Normal DL configuration
-- AcceptPathInfo On
-- AllowOverride Limit
-- Options -Indexes
-- DirectoryIndex index.php index.html
--
-- <FilesMatch "^(admin|rest)\.php$">
-- # Forward the credentials for the PHP process
-- RewriteEngine on
-- RewriteCond %{HTTP:Authorization} ^(.*)
-- RewriteRule ^(.*) - [E=HTTP_AUTHORIZATION:%1]
-- </FilesMatch>
--</Directory>
--
--
This is required to correctly pass the Authorization header to the PHP
--process.
--
If you want to enable HTTP/External authentication, just add the usual
--authorization configuration as well:
--
--<Directory /your-installation-directory>
-- # Normal DL configuration
-- AcceptPathInfo On
-- AllowOverride Limit
-- Options -Indexes
-- DirectoryIndex index.php index.html
-- <FilesMatch "^(admin|rest)\.php$">
-- # Forward the credentials for the PHP process
-- RewriteEngine on
-- RewriteCond %{HTTP:Authorization} ^(.*)
-- RewriteRule ^(.*) - [E=HTTP_AUTHORIZATION:%1]
--
-- # Require a Basic authentication scheme for admin/rest.php
-- AuthType Basic
-- AuthName "Restricted Area"
-- ...
-- Require valid-user
-- </FilesMatch>
--</Directory>
--
Nginx in combination with PHP/FastCGI works fine but needs special configuration to
--setup PATH_INFO correctly. Here is an example configuration with DL
--installed as a subdirectory in the document root:
--
--location ^~ /dl {
-- # Protect the include directories
-- location ~ ^/dl(?:/|/.*/)include {
-- deny all;
-- }
--
-- index index.php index.html;
-- try_files $uri $uri/ =404;
--
-- # Enable PHP
-- location ~ \.php(?:$|/) {
-- include fastcgi_params;
--
-- # Set maximum body size (should be the same as PHP's post_max_size)
-- client_max_body_size 512M;
--
-- # Setup PATH_INFO (http://trac.nginx.org/nginx/ticket/321)
-- fastcgi_split_path_info ^(.+\.php)(/.+)$;
-- set $path_info $fastcgi_path_info;
-- fastcgi_param PATH_INFO $path_info;
--
-- try_files $fastcgi_script_name =404;
--
-- fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
-- fastcgi_index index.php;
-- fastcgi_pass unix:/var/run/php5-fpm.sock;
-- }
--}
--
Ticket expiration can be either performed internally to DL (the default), or by
--using the external include/scripts/expire.php utility with a cron job. This
--preference can be set by controlling the $gcInternal parameter.
--
The internal method requires no setup, but the external method has the added
--advantage of not interrupting the web interface during the expiration process,
--and also ensures that the spool is emptied when DL itself is not used actively.
Expiration is usually performed aggressively at every page request. You can
--control this behavior (thus reducing the DB pressure) by tuning the
--$gcProbability and $gcLimit parameters.
--
If you notice too much load on your DB, start by lowering $gcProbability to
--0.5 and set $gcLimit to roughly the number of active tickets currently
--present in your DB.
--
Continue to lower $gcProbability even further until the load becomes
--acceptable. When the load is acceptable, but queries take too long, reduce
--$gcLimit.
Simply call include/scripts/expire.php within a cron job, which should be
--executed with the same user as the web server. Executing the script once a
--day is sufficient for low traffic websites, but can be executed as often as
--needed. $gcLimit still controls how many tickets are expired for each run
--to limit the execution time.
DL has been translated in several languages and will attempt to detect the
--correct locale of the browser and use it automatically when available. If no
--matching translation can be found, a default will be used, which is configured
--to be English in the main distribution. The user can however switch the
--language anytime.
--
Adding a new translation is easy for anyone familiar with the gettext tools:
--you don't need programming knowledge. If you want to contribute a new language,
--or suggest a better translation, we recommend to subscribe to the mailing list
--and ask for guidance. We really appreciate your help.
Edit htdocs/include/lang.php and add your new language name and alias to
--$langData, as done for the other languages.
--
--
Execute:
--
--cd htdocs/include/scripts/
--./langgen.php
--
--
to freshen the strings to be translated.
--
--
Translate the generated messages.po in the directory
--htdocs/include/locale/<locale_NAME>/LC_MESSAGES/ using a text editor, or
--by using PoEdit, or any other "po" editing tool.
--
--
Optionally translate the user guide, which is located in
--htdocs/include/static/guide/.
--
Copy the english directory tree into a new tree with the new locale name and
--translate index.rst. index.html is regenerated automatically.
DL should be usable by users without any training. The web interface must be
--self-explanatory. If you find the usage to be difficult or that the interface
--could be improved, it's a bug. Please let us know.
A command-line client to the REST interface is included in the distribution in
--client/dl-cli.py. This client requires a simple text configuration file, by
--default stored in ~/.dl.rc, containing the following values:
--
--
url: REST URL of the service
--
user: your user name
--
pass (optional): your password (if not specified, you will be prompted for it
--by the client)
--
passcmd (optional): invoke the supplied command to obtain the password
--
verify (optional): "true" or "false": enable/disable SSL verification
--(might be required for testing, but defaults to true)
--
email (optional): default email address for grant notifications
--
fingerprint: Validate the server against the specified certificate or
--fingerprint (See Public key pinning).
Simply run the command with no arguments to see usage information. At least
--Python 2.7 is required (with Python 3+ being recommended), with the "PycURL"
--and "ConfigObj" modules installed. Under Debian/Ubuntu systems you can install
--the required dependencies by doing the following:
A graphical client is also included in the distribution, which allows to create
--tickets easily from the system's taskbar. The client can be run by executing
--client/dl-wx/dl-wx.py or by downloading an executable client.
--
Upon first execution the user will be prompted for the basic configuration.
--After that all DL functions can be operated through the taskbar icon:
--
--
Left-clicking on the taskbar will create a new ticket using the default
--settings.
--
Right-clicking allows to select different actions.
--
On OSX, you can drop files directly on the dock.
--
--
At least Python 2.7 is required, with the "ConfigObj", "PycURL" and "wxPython"
--modules installed. Under Debian/Ubuntu systems you can install the required
--dependencies by doing the following:
The fingerprint option in the ~/.dl.rc configuration file implements
--public key pinning, and supports any value directly accepted by cURL.
--
It can be a path to a DER/PEM certificate file, or a SHA256 hash of the public
--key of the host. The hash can be either a hex-encoded string (with optional
--colon separators), or a string starting with sha256// and followed by a
--base64-encoded value of the hash.
--
The quickest way to obtain the fingerprint is to use curl directly:
The bundled extension "Thunderbird-Filelink-DL" integrates with the new
--Thunderbird's Filelink functionality, by using the REST service provided by DL
--0.10 and onward. The extension allows to convert large attachments to links
--automatically, directly within the Composer window.
--
The extension also allows the user to generate/insert a new upload grant in the
--current message from the composer window. Both a menu command (under "Tools" ..
--"Insert upload grant") and a toolbar item (that you manually need to drag in
--the composer toolbar) are provided.
--
To install the extension, go to Thunderbird's "Tools" .. "Addons" menu, and
--click on the "Settings" icon just next to the search bar. Select "Install
--Add-on from file..." and choose the file client/thunderbird-filelink-dl.xpi
--as provided in the distribution.
--
See full installation and usage instructions on the extension web page.
DL release (and release candidate) announcements (read-only list). Very low
--traffic. To subscribe, send an email to <dl-announces+subscribe@thregr.org>.
You are encouraged to change DL as you see fit under the terms of the GNU GPL 2
--license, or (at your option) any later version. DL's GIT repository is publicly
--accessible at:
Development releases directly downloaded from git do not include pre-processed
--files. To build the localization data gettext and docutils need to be
--installed. You'll then need to execute:
--
--cd htdocs/include/scripts/
--./langupd.php
--
--
To build the Thunderbird add-on, the Thunderbird SDK needs to be installed as
--well. You might need to change the paths inside
--client/thunderbird-filelink-dl/config_build.sh (which is tuned for Debian's
--thunderbird-dev package) and execute:
Database schema changes are not gracefully handled while following a
--development release. Do not run development releases on a production
--environment.
--
--
-diff -Nur dl-0.18.1/README.rst dl-master/README.rst
---- dl-0.18.1/README.rst 2017-09-06 12:08:38.000000000 -0400
-+++ dl-master/README.rst 2021-03-16 18:59:58.000000000 -0400
-@@ -302,7 +302,6 @@
- AuthType Basic
- AuthName "Restricted Area"
- Require valid-user
-- Satisfy any
-
- # You'll need to provide a valid source for passwords using either the
- # following or some other authentication source (such as LDAP)
-@@ -326,7 +325,6 @@
- AuthType Basic
- AuthName "Restricted Area"
- Require valid-user
-- Satisfy any
-
- # Use the LDAP provider (just an example query)
- AuthBasicProvider ldap
-@@ -697,7 +695,7 @@
- You can contact the main author directly at , though using
- the general list is encouraged.
-
--.. _GMane: http://www.gmane.org/
-+.. _GMane: https://news.gmane.io/
-
-
- Customisation and development
-diff -Nur dl-0.18.1/RESTAPI.html dl-master/RESTAPI.html
---- dl-0.18.1/RESTAPI.html 2017-09-06 12:09:40.000000000 -0400
-+++ dl-master/RESTAPI.html 1969-12-31 19:00:00.000000000 -0500
-@@ -1,656 +0,0 @@
--
--
--
--
--
--
--DL REST API
--
--
--
--
Every request is gated through the "/rest.php" page (or simply "/rest",
--depending on the configuration), which is directly on the root of the web
--service, for example:
--
--https://dl.example.com/rest.php
--
--
Each action is directly appended to the URI space, followed by parameters (if
--any):
--
--/rest/request[/parameters]
--
--
Every request must be performed via the appropriate HTTP method (either "GET"
--or "POST"), and must always include HTTP's "Basic" authorization credentials.
--
The credentials must also be replicated in a second header "X-Authorization"
--(which follows the same syntax as a normal "Basic" authorization scheme).
--
"POST" requests are x-www-form-urlencoded and must also include:
--
--
A JSON-encoded "msg" parameter, with arguments defined by the request. This
--parameter should always be present, even when empty.
--
When needed, a "file" parameter with the file to be attached.
--
--
The output of every request can be:
--
--
An HTTP error code only (400, 401, 500, etc).
--
--
An HTTP error code with a JSON-encoded message with an "error" term:
--
--{"error":"error description"}
--
--
--
A successful HTTP status (200), with a JSON-encoded message (even if empty)
--containing the specific request output.
@filename is a special curl syntax that specifies the path to the
--filename to be posted. The basic authorization data is provided manually, as
--it needs to be replicated in the non-standard header "X-Authorization" anyway
--(this is used as a secondary token to prevent CSRF). You can construct the
--authorization hash on the command-line as well with the following:
--
--echo -n 'user:password' | base64
--
--
Please keep in mind command-line arguments are usually visible to other users
--running on the same system, potentially exposing your password.
A Python API, supporting both asynchronous/synchronous operations and progress
--support can be found in the client/dl-wx/dl.py file. The API is used both
--by dl-wx.py and dl-cli.py in the same directory.
--
A simpler stand-alone implementation which can be helpful for testing can be
--found at client/dl-cli.py.
-+
-+
-+
-+
-+
-+