nobrend.ru Report : Visit Site

Technical data of the nobrend.ru

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host nobrend.ru. Currently, hosted in Russian Federation and its service provider is United Network LLC .

the related websites

canneslions.com lookatwhatimade.net advfn.com infoplease.com mckinsey.com thestudentsurvey.com sustainia.me cityandguilds.com businessesgrow.com theworlds50best.com 

HTTP Header Analysis

HTTP Header information is a part of HTTP protocol that a user's browser sends to called Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips mod_fcgid/2.3.9 PHP/5.4.16 containing the details of what the browser wants and will accept back from the web server.

DNS

HtmlToText

опыт одного админа… home about hp raid cli debian 8 jessie november 14th, 2016 shell echo 'deb http://downloads.linux.hpe.com/sdr/repo/mcp/debian jessie/current non-free' > /etc/apt/sources.list.d/hp.proliant.list curl http://downloads.linux.hpe.com/sdr/hpepublickey2048_key1.pub | apt-key add - curl http://downloads.linux.hpe.com/sdr/hppublickey2048_key1.pub | apt-key add - apt-get install hpssacli 1 2 3 4 echo 'deb http://downloads.linux.hpe.com/sdr/repo/mcp/debian jessie/current non-free' > / etc / apt / sources .list .d / hp .proliant .list curl http : / / downloads .linux .hpe .com / sdr / hpepublickey2048_key1 .pub | apt - key add - curl http : / / downloads .linux .hpe .com / sdr / hppublickey2048_key1 .pub | apt - key add - apt - get install hpssacli posted in system administration , uncategorized | no comments » список публичных ntp серверов november 28th, 2015 shell россия ntp1.vniiftri.ru ipv4 udp 123 stratum 1 ntp2.vniiftri.ru ipv4 udp 123 stratum 1 ntp3.vniiftri.ru ipv4 udp 123 stratum 1 ntp4.vniiftri.ru ipv4 udp 123 stratum 1 ntp21.vniiftri.ru ipv4 udp 123 stratum 2 ntp1.niiftri.irkutsk.ru ipv4 udp 123 stratum 1 ntp2.niiftri.irkutsk.ru ipv4 udp 123 stratum 1 vniiftri.khv.ru ipv4 udp 123 stratum 1 vniiftri2.khv.ru ipv4 udp 123 stratum 1 ntp0.zenon.net gps-источник gps-time.prao.psn.ru gps-источник ntp.mobatime.ru gps-источник сша time.nist.gov атомные часы ntp.nasa.gov gps-источник япония ntp.nict.jp атомные часы 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 россия ntp1 .vniiftri .ru ipv4 udp 123 stratum 1 ntp2 .vniiftri .ru ipv4 udp 123 stratum 1 ntp3 .vniiftri .ru ipv4 udp 123 stratum 1 ntp4 .vniiftri .ru ipv4 udp 123 stratum 1 ntp21 .vniiftri .ru ipv4 udp 123 stratum 2 ntp1 .niiftri .irkutsk .ru ipv4 udp 123 stratum 1 ntp2 .niiftri .irkutsk .ru ipv4 udp 123 stratum 1 vniiftri .khv .ru ipv4 udp 123 stratum 1 vniiftri2 .khv .ru ipv4 udp 123 stratum 1 ntp0 .zenon .net gps - источник gps - time .prao .psn .ru gps - источник ntp .mobatime .ru gps - источник сша time .nist .gov атомные часы ntp .nasa .gov gps - источник япония ntp .nict .jp атомные часы posted in system administration | no comments » restricting solr with jetty to localhost november 11th, 2014 if you want to try apache solr, the easiest way to get started is to use the example the comes with the download. just run java -jar start.jar and you can start searching like a pro. however, the integrated jetty server is configured to bind to port 8983 on all ip adresses by default. this configuration is unsafe: anyone could clear your whole solr index! it is a good idea to let the server listen (bind) only on localhost, unless your server is in a private network. a quick solution is to set the system properties jetty.host and jetty.port on startup, e.g. like that: shell java -djetty.host=127.0.0.1 -djetty.port=1337 -jar start.jar 1 java - djetty .host = 127.0.0.1 - djetty .port = 1337 - jar start .jar alternatively, you can edit the configuration at example/etc/jetty.xml. look for these lines: xhtml <set name="host"><systemproperty name="jetty.host" /></set> <set name="port"><systemproperty name="jetty.port" default="8983"/></set> 1 2 <set name = "host" > <systemproperty name = "jetty.host" /> </set> <set name = "port" > <systemproperty name = "jetty.port" default = "8983" /> </set> posted in jetty | no comments » could not load host key: /etc/ssh/ssh_host_ecdsa_key november 9th, 2014 if you get error message : ‘could not load host key: /etc/ssh/ssh_host_ecdsa_key’ when restarting ssh, after an upgrade from freebsd 8.x to 9.x you need to create new ecdsa key with following command #ssh-keygen -t ecdsa -f /etc/ssh/ssh_host_ecdsa_key -n then you should restart the sshd service #/etc/rc.d/sshd restart posted in freebsd | no comments » nginx direct file upload without passing them through backend april 16th, 2014 it’s pretty straightforward to manage file upload. everybody can do it with using multipart/form-data encoding rfc 1867. let’s see what happens: client sends post request with the file content in body webserver accepts the request and initiates data transfer (or returns error 413 if the file size is exceed the limit) webserver starts to populate buffers (depends on file and buffers size), store it on disk and send it via socket/network to back-end back-end verifies the authentication (take a look, once file is uploaded) back-end reads the file and cuts few headers content-disposition, content-type, stores it on disk again back-end performs all you need to do with the file too much overhead? it happens all the time you upload something. the problems are obvious: authentication happens on back-end after the file being saved on disk by webserver the body request saves on disk twice (on web-server and back-end sides both) back-end blocks while eating your file resulted binary-data rarely required by back-end itself, because images usually use by imagemagic, documents upload on s3 or something else to be honest i can see no problem due to small file size upload. but what if you handle big files upload all the time? let’s assume you use nginx web-server, so you have several options: nginx-upload-module widely used, but not supported with nginx 1.3.9+ nginx-big-upload too young, nobody uses it in production yet lua-resty-upload requires few external dependencies clientbodyinfileonly nginx built-in functionality the best and production-ready solution is the last one, clientbodyinfileonly. due to lack of documentation nobody uses it, but let me share with experience how to setup it. first of all you need to use premature authentication before file uploading is started – basic http authentication (shared password) or httpauthrequest module (for back-end authentication through headers). then update nginx configuration with the following config: location /upload { auth_basic "restricted upload"; auth_basic_user_file basic.htpasswd; limit_except post { deny all; } client_body_temp_path /tmp/; client_body_in_file_only on; client_body_buffer_size 128k; client_max_body_size 1000m; proxy_pass_request_headers on; proxy_set_header x-file $request_body_file; proxy_set_body off; proxy_redirect off; proxy_pass http://backend/file; } once you reload nginx, the new url /upload is ready to accept file upload without any back-end interaction, it all goes through nginx and send callback to http://backend/file with file name in x-file header. it’s all, easy? you already know the file name before you make post request, so you should preserve it until the back-end receive it. we do use extra headers with post that pass through nginx proxy and comes to back-end unmodified. for instance, having x-name headers from initial requests help you to catch it up on backend. if you need to have back-end authentication, only way to handle is to use auth_request, for instance: location = /upload { auth_request /upload/authenticate; ... } location = /upload/authenticate { internal; proxy_set_body off; proxy_pass http://backend; } upload request should come with headers to be validated, for instance x-api-key, once authentication is finished, nginx started to file uploading and pass the file name to backend afterward. it’s internal cascade of requests, so you have to do only one request with file body and authentication headers. the good news that auth_request module will be incorporated in the nginx core soon, so we can use it without ./configure … –add-module=/tmp/ngxhttpauth_request p.s. clientbodyinfileonly incompatible with multi-part data upload, so you can use it via xmlhttprequest2 (without multi-part) and binary data upload only curl –data-binary ‘@file’ http://localhost/upload this method is prefer to use with native mobile applications that handle big file upload all the time. источник posted in nginx | no comments » remove the ^m character at the end of text files april 16th, 2014 $ cat filename | col -b > newfilename posted in f

URL analysis for nobrend.ru

http://nobrend.ru/?p=252
http://nobrend.ru/?p=355
http://nobrend.ru/?p=256
http://nobrend.ru/?p=255
http://nobrend.ru/?p=254
http://nobrend.ru/?m=200901
http://nobrend.ru/?p=156#comment-6469
http://nobrend.ru/?cat=18
http://nobrend.ru/?cat=11
http://nobrend.ru/?m=200810
http://nobrend.ru/?m=201006
http://nobrend.ru/?p=231
http://nobrend.ru/?m=200903
http://nobrend.ru/?cat=20
http://nobrend.ru/?p=156#comment-6477

Whois Information

Whois is a protocol that is access to registering information. You can reach when the website was registered, when it will be expire, what is contact details of the site with the following informations. In a nutshell, it includes these informations;

% By submitting a query to RIPN's Whois Service
% you agree to abide by the following terms of use:
% http://www.ripn.net/about/servpol.html#3.2 (in Russian)
% http://www.ripn.net/about/en/servpol.html#3.2 (in English).

domain: NOBREND.RU
nserver: pns6.cloudns.net.
nserver: pns7.cloudns.net.
nserver: pns8.cloudns.net.
nserver: pns9.cloudns.net.
state: REGISTERED, DELEGATED, VERIFIED
person: Private Person
registrar: R01-RU
admin-contact: https://partner.r01.ru/contact_admin.khtml
created: 2006-08-05T20:00:00Z
paid-till: 2018-08-05T21:00:00Z
free-date: 2018-09-06
source: TCI

Last updated on 2018-01-25T01:06:34Z


  REFERRER http://www.ripn.net

  REGISTRAR RUCENTER-REG-RIPN

SERVERS

  SERVER ru.whois-servers.net

  ARGS nobrend.ru

  PORT 43

  TYPE domain

DISCLAIMER
By submitting a query to RIPN's Whois Service
you agree to abide by the following terms of use:
http://www.ripn.net/about/servpol.html#3.2 (in Russian)
http://www.ripn.net/about/en/servpol.html#3.2 (in English).

DOMAIN

  NAME nobrend.ru

NSERVER

  PNS6.CLOUDNS.NET 185.136.97.111

  PNS7.CLOUDNS.NET 185.136.98.111

  PNS8.CLOUDNS.NET 185.136.99.111

  PNS9.CLOUDNS.NET 185.136.96.111

  STATUS REGISTERED, DELEGATED, VERIFIED

  CREATED 2006-08-05

  EXPIRES 2018-08-05

  SOURCE TCI

  REGISTERED yes

Mistakes

The following list shows you to spelling mistakes possible of the internet users for the website searched .