kodono.info rapport :   Visitez le site

Données techniques du kodono.info

Geo IP vous fournit comme la latitude, la longitude et l'ISP (Internet Service Provider) etc. informations. Notre service GeoIP a trouvé l'hôte kodono.info.Actuellement, hébergé dans France et son fournisseur de services est OVH SAS .

the related websites

domaine	Titre
sportou.bzh	aucun titre
bydesigngifts.ca	aucun titre
le-clebstomane.com	aucun titre
propagandes.info	aucun titre
lormar-lannion.bzh	aucun titre
stp-enseignes.com	aucun titre
ganaderialagarrocha.com	aucun titre
robustrecords.net	aucun titre
networkvisio.com	aucun titre
emicrocredit.com	aucun titre
revetement-sol-mur.com	aucun titre
sejoursvoyagesturquie.com	aucun titre
post-dream.com	aucun titre
flox-corporate.com	aucun titre
agencetheatre.com	aucun titre

Analyse d'en-tête HTTP

Les informations d'en-tête HTTP font partie du protocole HTTP que le navigateur d'un utilisateur envoie à appelé Apache contenant les détails de ce que le navigateur veut et acceptera de nouveau du serveur Web.

DNS

HtmlToText

kodono pour tous les technophiles -- home a propos greasemonkey howto github performance javascript sharepointplus 9 juil sharepoint daterangesoverlap value posté par aymeric le lundi 9 juillet 2018 publié dans english partager sur (this is a copy of a post that is not available anymore) daterangesoverlap value type i don’t know if any back-end developers have run into this same issue when working with the spquery to pull expanded recurrence date, but from here, not all daterangesoverlap value types work the way they should. and they’re cryptically-documented, where mentioned at all. the basics are that you can return dates that “overlap” a given scenario. the overlapping varies depending on scenario, as follows: <year /> this is supposed to get all events within: (a) today’s year (if no calendardate is passed), or (b) the date passed in queryoptions as calendardate. actually, it returns all dates from [today] into the future. it ignores: (a) the calendardate, and (b) the end of the current year <month /> performs consistently as expected, with the exception that its definition of “month” is more of a “month view.” a month view consists of all of the weeks which contain days in that month. in other words, the month view for may 2012 begins on april 29, 2012, because may 1 is on a tuesday and the “month view” consists of full weeks. likewise, the may 2012 month view ends on june 5, 2012. this means that pulling all of the dates for may 2012 will return all events for april 29 – june 5. however, even though april 29 is the beginning of the may month view, when passed as the calendardate, it will return the april month view. see below for how this affects date calculations based on pulling data for a given month. <week /> performs exactly like <month />, but only returns the corresponding week for: (a) today, or (b) calendardate <today /> returns just the events for today. <now /> contrary to most documentation, <now /> doesn’t “work” but rather defaults to the same results as <year />. in fact, <year /> is the default. if you leave off the entire where clause, but include the recurrencedate and frecurrence fields and the queryoptions (calendardate will be ignored), you get the same results as <year />. calendardate in queryoptions, if the calendardate is set, it needs the date to be a string in the format: yyyy-mm-ddthh:mm:ssz in most cases, setting the calendardatewhen needed to the real date on which you want to base your range will work just fine, as long as you set the time in the z-notation to noon. the reason for the noontime setting is to make allowance for all-day events within the given range. these tend to get messed up when viewing is based on a midnight or early morning time. basing the range on noon alleviates the issue. (at least it does for us time zones; i confess that i haven’t tested them all.) tags: english , sharepoint no comment 28 avr interclassement mysql pour le français posté par aymeric le samedi 28 avril 2018 publié dans français partager sur quel interclassement (dit aussi collation ) choisir pour sa base mysql afin d’y enregistrer des caractères français (entre autres) ? l’interclassement a deux fonctions : permettre l’ordonnancement correct d’une liste de caractères (pour indiquer que le “é” vient après le “e”, ou que les majuscules viennent avant les minuscules, etc) permettre de savoir quand un caractère est “équivalent” à un autre (dans les requêtes where que, par exemple, le caractère “e” est équivalent à “e”, “é”, “è” ou “ê”) sur fluxbb on retrouve une très bonne explication. je copie qu’une partie, mais allez lire cet article vraiment complet : mysql permet de choisir comment les données seront classées (order by) par ce qui est appelé une « collation » (collate). ceci permet de répondre, par exemple, au problème classique de la sensibilité à la casse : les majuscules doivent-elles précéder les minuscules, ou bien faut-il considérer a et a comme de même valeur ? la sensibilité aux accents : comptent-ils dans le tri ? font-ils une différence lors de la recherche ? la possibilité qu’un caractère (ligature oe) puisse correspondre à plusieurs (o suivi de e) : c’est ce qu’unicode appelle « l’expansion ». toutes les collations ont un nom qui commence par le jeu de caractère auquel elles sont liées, et se terminent par l’une de ces trois abréviations : _bin comme binary : les caractères sont dans l’ordre de leurs numéros de code (ce qui donne d’abord toutes les majuscules, puis toutes les minuscules, puis les lettres accentuées, en vrac). _cs comme case sensitive : les caractères sont triés selon le ou les langages de référence, mais de manière sensible à la casse. _ci comme case insensitive : idem, mais en ignorant la casse. il est possible de définir plusieurs niveaux : de la colonne jusqu’à toute la base de données. ainsi on peut définir une collation pour une colonne qui sera différente de celle de la table. au final, on peut utiliser utf8_unicode_ci : utf8 indique qu’on peut enregistrer une large palette de caractères (on utilisera utf8mb4 si on souhaite enregistrer des émoticones en plus), unicode_ci va permettre un bon tri tout en ignorant la casse. tags: français , mysql no comment 25 avr content security policy (csp) blocks scripts from violentmonkey / greasemonkey posté par aymeric le mercredi 25 avril 2018 publié dans astuce , english partager sur i wanted to inject some codes on github, however i received content security policy errors. it’s because github blocks this kind of injected code. to bypass this restriction i installed the addon content security policy override (if you have firefox you can install this chrome addon using chrome store foxified ) then i applied the below rule in the addon’s settings : [ ["https://github\\.com/*", [ ["script-src", "script-src 'self' 'unsafe-inline' 'unsafe-eval'"] ]] ] now my violentmonkey script works. tags: astuce , english no comment 19 avr remove custom properties/metadata for an office document [javascript] posté par aymeric le jeudi 19 avril 2018 publié dans english , niveau expert , programmation partager sur i have this document library on sharepoint where i have one custom column called metadata and that is a lookup to another list on my sharepoint. when the users download an office document from this library and then re-upload it we could have the below error message: there is at least one lookup column that enforces a relationship behavior and contains values that reference one or more non-existent items in the target list. it’s because the office documents keep the custom columns from the document library from where they have been downloaded… in that case the file tries to reassign the metadata with an id that doesn’t exist anymore… causing this issue! because i’m using a homemade interface to upload documents, i’ve been able to pass some code to delete the file’s properties on-the-fly before pushing it into the document library. to do so, you need jszip that will permit to unzip the office document in order to retrieve the file docprops/custom.xml and to change the properties we want before the final upload. let’s imagine my page contains an <input type="file"> , and that i have already loaded jszip. then i use filereader : var filereader = new filereader(); filereader.onloadend = function(e) { // content is the "arraybuffer" that represents my file var content = e.target.result; // check the file's extension (here "docx", "xlsx", and "pptx", but we could add more extensions var ext=file.name.split(".").slice(-1)[0]; switch (ext) { case "docx": case "xlsx": case "pptx": { // load content in jszip jszip.loadasync(content) .then(function(zip) { // unzip the file that contains metadata/properties return zip.file("docprops/custom.xml").async("text") .then(function(txt) { // replace the faulty column txt = txt.replace(/name="metadata"><vt:lpwstr>\d+<\/vt:lpwstr>/,'name="metadata">

Informations Whois

Whois est un protocole qui permet d'accéder aux informations d'enregistrement.Vous pouvez atteindre quand le site Web a été enregistré, quand il va expirer, quelles sont les coordonnées du site avec les informations suivantes. En un mot, il comprend ces informations;

Domain Name: KODONO.INFO
Registry Domain ID: D28219045-LRMS
Registrar WHOIS Server:
Registrar URL: http://www.ovh.com/
Updated Date: 2017-03-28T12:42:10Z
Creation Date: 2009-04-04T12:37:21Z
Registry Expiry Date: 2020-04-04T12:37:21Z
Registrar Registration Expiration Date:
Registrar: OVH sas
Registrar IANA ID: 433
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Reseller:
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: C200503110-LRMS
Registrant Name: Aymeric de ViviAs
Registrant Organization:
Registrant Street: office #7767615
Registrant Street: c/o OwO, BP80157
Registrant City: Roubaix Cedex 1
Registrant State/Province:
Registrant Postal Code: 59053
Registrant Country: FR
Registrant Phone: +33.972101007
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: t9miyr4dtjvx1taecz7n@h.o-w-o.info
Registry Admin ID: C200503111-LRMS
Admin Name: Aymeric de Vivies
Admin Organization:
Admin Street: office #7767615
Admin Street: c/o OwO, BP80157
Admin City: Roubaix Cedex 1
Admin State/Province:
Admin Postal Code: 59053
Admin Country: FR
Admin Phone: +33.972101007
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: 5evrebi5fafem56f58jl@i.o-w-o.info
Registry Tech ID: C200503111-LRMS
Tech Name: Aymeric de Vivies
Tech Organization:
Tech Street: office #7767615
Tech Street: c/o OwO, BP80157
Tech City: Roubaix Cedex 1
Tech State/Province:
Tech Postal Code: 59053
Tech Country: FR
Tech Phone: +33.972101007
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: 5evrebi5fafem56f58jl@i.o-w-o.info
Registry Billing ID: C200503111-LRMS
Billing Name: Aymeric de Vivies
Billing Organization:
Billing Street: office #7767615
Billing Street: c/o OwO, BP80157
Billing City: Roubaix Cedex 1
Billing State/Province:
Billing Postal Code: 59053
Billing Country: FR
Billing Phone: +33.972101007
Billing Phone Ext:
Billing Fax:
Billing Fax Ext:
Billing Email: 5evrebi5fafem56f58jl@i.o-w-o.info
Name Server: DNS100.OVH.NET
Name Server: NS100.OVH.NET
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2017-07-18T09:24:46Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

Access to AFILIAS WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the Afilias registry database. The data in this record is provided by Afilias Limited for informational purposes only, and Afilias does not guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to(a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Afilias except as reasonably necessary to register domain names or modify existing registrations. All rights reserved. Afilias reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.

  REFERRER http://whois.afilias.info

  REGISTRAR Afilias Global Registry Services

SERVERS

  SERVER info.whois-servers.net

  ARGS kodono.info

  PORT 43

  TYPE domain
RegrInfo
DOMAIN

  NAME kodono.info

  HANDLE D28219045-LRMS

  CREATED 2009-04-04

STATUS
clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
clientTransferProhibited https://icann.org/epp#clientTransferProhibited

NSERVER

  DNS100.OVH.NET 213.251.188.144

  NS100.OVH.NET 213.251.128.144

OWNER

  HANDLE C200503110-LRMS

  NAME Aymeric de ViviAs

ADDRESS

STREET
office #7767615
c/o OwO, BP80157

  CITY Roubaix Cedex 1

  PCODE 59053

  COUNTRY FR

  PHONE +33.972101007

  EMAIL t9miyr4dtjvx1taecz7n@h.o-w-o.info

ADMIN

  HANDLE C200503111-LRMS

  NAME Aymeric de Vivies

ADDRESS

STREET
office #7767615
c/o OwO, BP80157

  CITY Roubaix Cedex 1

  PCODE 59053

  COUNTRY FR

  PHONE +33.972101007

  EMAIL 5evrebi5fafem56f58jl@i.o-w-o.info

TECH

  HANDLE C200503111-LRMS

  NAME Aymeric de Vivies

ADDRESS

STREET
office #7767615
c/o OwO, BP80157

  CITY Roubaix Cedex 1

  PCODE 59053

  COUNTRY FR

  PHONE +33.972101007

  EMAIL 5evrebi5fafem56f58jl@i.o-w-o.info

BILLING

  HANDLE C200503111-LRMS

  NAME Aymeric de Vivies

ADDRESS

STREET
office #7767615
c/o OwO, BP80157

  CITY Roubaix Cedex 1

  PCODE 59053

  COUNTRY FR

  PHONE +33.972101007

  EMAIL 5evrebi5fafem56f58jl@i.o-w-o.info

  REGISTERED yes

Erreurs

La liste suivante vous montre les fautes d'orthographe possibles des internautes pour le site Web recherché.