restrserve.org valuation and analysis
Robots.txt Information
| Robot | Path | Permission |
| GoogleBot | / | ✔ |
| BingBot | / | ✔ |
| BaiduSpider | / | ✔ |
| YandexBot | / | ✔ |
Meta Tags
| Title | A Framework for Building HTTP API • |
| Description | RestRserve Toggle navigation RestRserve 1.2.1 Get started Reference Articles Authentication Body encoding and decoding Logging Middleware Benchmarks Changelog RestRs |
| Keywords | N/A |
Server Information
| WebSite | |
| Host IP | 185.199.108.153 |
| Location | - |
Related Websites
| Site | Rank |
More to Explore
restrserve.org Valuation
|
US$1,701,727
Last updated: 2023-05-16 11:01:50
restrserve.org has Semrush global rank of 6,219,744. restrserve.org has an estimated worth of US$ 1,701,727, based on its estimated Ads revenue. restrserve.org receives approximately 196,354 unique visitors each day. Its web server is located in -, with IP address 185.199.108.153. According to SiteAdvisor, restrserve.org is safe to visit. |
Traffic & Worth Estimates
| Purchase/Sale Value | US$1,701,727 |
| Daily Ads Revenue | US$1,571 |
| Monthly Ads Revenue | US$47,125 |
| Yearly Ads Revenue | US$565,497 |
| Daily Unique Visitors | 13,091 |
| Note: All traffic and earnings values are estimates. | |
DNS Records
| Host | Type | TTL | Data |
| restrserve.org. | A | 300 | IP: 185.199.108.153 |
| restrserve.org. | A | 300 | IP: 185.199.109.153 |
| restrserve.org. | NS | 300 | NS Record: ns1kwy.name.com. |
| restrserve.org. | NS | 300 | NS Record: ns2fjz.name.com. |
| restrserve.org. | NS | 300 | NS Record: ns3qty.name.com. |
| restrserve.org. | NS | 300 | NS Record: ns4lqx.name.com. |
HtmlToTextCheckTime:2023-05-16 11:01:50
| Toggle navigation RestRserve 1.2.1 Get started Reference Articles Authentication Body encoding and decoding Logging Middleware Benchmarks Changelog RestRserve RestRserve is an R web API framework for building high-performance AND robust microservices and app backends. On UNIX-like systems and Rserve backend RestRserve handles requests in parallel: each request in a separate fork - credits go to Simon Urbanek . Quick start Creating application is as simple as: library ( RestRserve ) app = Application $ new ( ) app $ add_get ( path = "/health" , FUN = function ( .req , .res ) { .res $ set_body ( "OK" ) } ) app $ add_post ( path = "/addone" , FUN = function ( .req , .res ) { result = list ( x = .req $ body $ x + 1L ) .res $ set_content_type ( "application/json" ) .res $ set_body ( result ) } ) backend = BackendRserve $ new ( ) backend $ start ( app , http_port = 8080 ) Test it with curl : curl localhost:8080/health # OK curl -H "Content-Type: application/json" -d ’{"x":10}’ |
HTTP Headers
HTTP/1.1 301 Moved Permanently Server: GitHub.com Content-Type: text/html Location: https://restrserve.org/ X-GitHub-Request-Id: B232:B4CC:ED4379:F42C48:61ED21C6 Content-Length: 162 Accept-Ranges: bytes Date: Sun, 23 Jan 2022 09:37:10 GMT Via: 1.1 varnish Age: 0 Connection: keep-alive X-Served-By: cache-hel1410028-HEL X-Cache: MISS X-Cache-Hits: 0 X-Timer: S1642930631.679797,VS0,VE108 Vary: Accept-Encoding X-Fastly-Request-ID: 136d597518ea48639e4803dfbc296ab480380c3a HTTP/2 200 server: GitHub.com content-type: text/html; charset=utf-8 last-modified: Tue, 22 Dec 2020 14:06:20 GMT access-control-allow-origin: * strict-transport-security: max-age=31556952 etag: "5fe1fd5c-4d65" expires: Sun, 23 Jan 2022 09:47:10 GMT cache-control: max-age=600 x-proxy-cache: MISS x-github-request-id: 90E8:8DE6:22DDDD:26CB38:61ED21C6 accept-ranges: bytes date: Sun, 23 Jan 2022 09:37:10 GMT via: 1.1 varnish age: 0 x-served-by: cache-hel1410030-HEL x-cache: MISS x-cache-hits: 0 x-timer: S1642930631.864824,VS0,VE112 vary: Accept-Encoding x-fastly-request-id: 3b2c9f281e484d514574183b8586649756292894 content-length: 19813 |
restrserve.org Whois Information
WHOIS LIMIT EXCEEDED - SEE WWW.PIR.ORG/WHOIS FOR DETAILS |