IceCodeNew

const https = require("https");

const token = ""; // change this to you telegram bot token!
const chatId = ""; // change this to your telegram chat id!
const cookie = ""; // change this to your shanbay cookie!

const PATH_API = (page) =>
  `/wordsapp/user_material_books/blozps/learning/words/today_learning_items?ipp=10&page=${page}&type_of=NEW`;

const options = {

IceCodeNew

addEventListener('fetch', event => event.respondWith(handleRequest(event.request)));

// Add environment variable `TGBOT_TOKEN` via Worker-Settings
async function requestTelegramBotAPI(method, payload) {
    return fetch(`https://api.telegram.org/bot${TGBOT_TOKEN}/${method}`, {
        method: "POST",
        headers: {
            "Content-Type": "application/json; charset=utf-8"
        },
        body: !payload ? undefined : JSON.stringify(payload)

IceCodeNew

# K4YT3X Server/Community zshrc
# Version 2020.06.15
#
# Licensed under the GNU General Public License Version 3 (GNU GPL v3),
#     available at: https://www.gnu.org/licenses/gpl-3.0.txt
# (C) 2018-2020 K4YT3X
#
# Gist Page: https://gist.github.com/k4yt3x/3b41a1a65f5d3087133e449793eb8858
# Short URL: akas.io/z
# Quick Install: curl -LsSf akas.io/z -o ~/.zshrc

IceCodeNew

ipa

Description

ipa is a shell function that will display the distilled informaiton from the ip a command.

Screenshots

IceCodeNew

Web Service Fronting

Multiple Web properties on a single IP address

Hosting multiple websites on a single public IP address on the standard HTTP(S) ports is relatively easy with popular web servers like Apache, Nginx and lighttpd all supporting Virtual Hosts.
For Web Services which bundle their own HTTP server, things get more complicated, unless their HTTP stack can be shared somehow. More often than not, the application's HTTP stack listens directly on a dedicated TCP port.

Hosting multiple services on a single IP then requires using a fronting server listening on the standard HTTP port, and routing to the right backend service based on the host name or the path sent by the client.
Path based routing is cumbersome, usually requiring either the service to be aware of the path prefix, or a rewrite by the HTTP fronting server of all absolute URLs in the requests and responses.
Hostname based routing is more straightforward. The fronting server can just look at the [HTTP/1.1 Host header](https://tools

IceCodeNew

server {
	listen 80;
	listen 443;
	listen [::]:80;
	listen [::]:443;
	
	server_name fonts.lug.ustc.edu.cn;
	access_log	/var/log/nginx/revproxy_access.log;
	error_log	/var/log/nginx/revproxy_error.log;
	

IceCodeNew

#
# This is the ultimate HAProxy 2.0 "Getting Started" config
# It demonstrates many of the features available which are now available 
# While you may not need all of these things, this can serve
# as a reference for your own configurations.
#
# Have questions?  Check out our community Slack:
# https://slack.haproxy.org/
#

IceCodeNew

# encoding: utf-8
# USE AT OWN RISK

#
# Follow this guide to install Ruby on Windows (step 1 and 2): https://forwardhq.com/support/installing-ruby-windows
# Install gems (with admin cmd prompt): 
#	https://rubygems.org/gems/bencode
#	https://rubygems.org/gems/rest_client
#
# Edit datpath below to point to your utorrent resume.dat file

IceCodeNew

#!/usr/bin/env sh

adb shell settings put global captive_portal_fallback_url http://g.cn/generate_204
adb shell settings put global captive_portal_http_url http://www.google.cn/generate_204
adb shell settings put global captive_portal_https_url https://www.google.cn/generate_204
adb shell settings put global captive_portal_other_fallback_urls http://www.qualcomm.cn/generate_204