Tag: ‘X-Requested-With’]

Nginx as a chain proxy with stunnel+pproxy+tor for add|set http headers responds with 400 status code

Post author By Server Questions
Post date December 24, 2020
No Comments on Nginx as a chain proxy with stunnel+pproxy+tor for add|set http headers responds with 400 status code

My initial goal is creating working http(ssl) proxy based on TOR socks5 connection first I up python-proxy with self-signed key then chained stunnel for securing connection, it works but cannot handle wss connection and seems like needs this headers patch ‘Access-Control-Allow-Origin’ ‘*’ … I didn’t find info how to do that using stunnel config, so […]

Tags 'X-Requested-With'], "?" 2020/12/24 10:33:58 [debug] 142472#142472: *3 http set discard body 2020/12/24 10:33:58 [debug] 142472#142472: *3 xslt filter header 2020, 24 Dec 2020 08:33:58 GMT Content-Type: text/html Content-Length: 166 Connection: close I am confused with this debug log ... could someone e, A[1], avail:-1 2020/12/24 10:33:58 [debug] 142472#142472: *3 recv: fd:20 205 of 1024 2020/12/24 10:33:58 [debug] 142472#142472: *3 reusable connect, c:1 2020/12/24 10:33:58 [debug] 142472#142472: *3 event timer del: 20: 142048169 2020/12/24 10:33:58 [debug] 142472#142472: *3 http special r, Cache-Control, client: 127.0.0.1, Content-Type'; } if ($request_method = 'CONNECT') { add_header 'Access-Control-Allow-Origin' '*'; }, Content-Type'; } if ($request_method = 'GET') { add_header 'Access-Control-Allow-Origin' '*'; add_hea, Content-Type'; # # Tell client that this pre-flight info is valid for 20 days # add_header 'A, If-Modified-Since, it works but cannot handle wss connection and seems like needs this headers patch 'Access-Control-Allow-Origin' '*' ... I didn't find info ho, Keep-Alive, My initial goal is creating working http(ssl) proxy based on TOR socks5 connection first I up python-proxy with self-signed key then chained, OPTIONS'; # # Custom headers and headers various browsers *should* be OK with but aren't # ad, OPTIONS'; add_header 'Access-Control-Allow-Headers' 'DNT, post, ready: 0 2020/12/24 10:33:58 [debug] 142472#142472: posix_memalign: 000055C8D4399B60:512 @16 2020/12/24 10:33:58 [debug] 142472#142472: *3 ac, request: "CONNECT stackoverflow.com:443 HTTP/1.1" 2020/12/24 10:33:58 [debug] 142472#142472: *3 http finalize request: 400, server, so started to dig nginx way (as a next chained proxy) nginx vhost config: # Virtual Host configuration for stunnel+pproxy+tor # https://doc, User-Agent, X-CustomHeader

Mastering Development

cors blocked errors when loading iframe in vue component, maybe use axios to mimic iframe?

Post author By Full Stack
Post date December 23, 2020
No Comments on cors blocked errors when loading iframe in vue component, maybe use axios to mimic iframe?

I’m doing some testing locally so my dev url is http://localhost:3000, I’m wanting to add an iframe into my vue component to bring in data from an outside domain. But I’m getting a cors errors being blocked, etc. I do have access to the domain and server I’m accessing so I have added <VirtualHost *:443> […]

Tags 'GET, 'X-Requested-With'], content-type" Header add Access-Control-Allow-Methods "PUT, DELETE, etc. I do have access to the domain and server I'm accessing so I have added ... Header add Access-Control-Allow-Or, I'm doing some testing locally so my dev url is http://localhost:3000, I'm not completely sure how to render the html from the axios call in vue. anyone have any suggestions on a possible solution?, I'm wanting to add an iframe into my vue component to bring in data from an outside domain. But I'm getting a cors errors being blocked, L] but even with that I still get cors error Uncaught DOMException: Blocked a frame with origin "http://localhost:3000" from accessing a cr, OPTIONS" ... RewriteEngine On RewriteCond %{REQUEST_METHOD} OPTIONS RewriteRule ^(.*)$ $1 [R=200, post

Mastering Development

‘from’ parameter not supported c++ libcurl mailgun api

Post author By Full Stack
Post date December 14, 2020
No Comments on ‘from’ parameter not supported c++ libcurl mailgun api

I’m trying to send a email with the mailgun api using c++ libcurl. The api is returning the error "message": "’from’ parameter is not a valid address. please check documentation". code CURL* curl; CURLcode res; std::string readBuffer; std::string user = "api:" + (std::string)"MY_API_KEY"; std::string data = "from=’from=’\"Bob Marley\" <bob@host.com>’&to=’jlkrumholz01@gmail.com’&subject=’Hello’&test=’hi’"; curl = curl_easy_init(); if (curl) { […]

Tags 'PUT', 'X-Requested-With'], "{}"); curl_easy_setopt(curl, "https://api.mailgun.net/v3/MY_SANDBOX_URL.mailgun.org/messages"); curl_easy_setopt(curl, 11 Dec 2020 22:06:32 GMT < Server: nginx < Content-Length: 86 < Connection: keep-alive < * STATE: PERFORM => DONE handle 0xaf50b0; line 2393, 1L); curl_easy_setopt(curl, 1L); res = curl_easy_perform(curl); curl_easy_cleanup(curl); std::cout << readBuffer << std::endl; } return, Authorization < Access-Control-Allow-Methods: GET, CURLOPT_COPYPOSTFIELDS, CURLOPT_POST, CURLOPT_SSL_VERIFYPEER, CURLOPT_URL, CURLOPT_USERPWD, CURLOPT_VERBOSE, CURLOPT_WRITEDATA, CURLOPT_WRITEFUNCTION, data.c_str()); curl_easy_setopt(curl, DELETE, false); curl_easy_setopt(curl, family1 == v6 * Trying 44.239.120.133:443... * STATE: WAITRESOLVE => WAITCONNECT handle 0xaf50b0; line 1924 (connection #0) * Connected to, I'm trying to send a email with the mailgun api using c++ libcurl. The api is returning the error "message": "'from' parameter is not a valid, need more data * STATE: SENDPROTOCONNECT => PROTOCONNECT handle 0xaf50b0; line 2008 (connection #0) * schannel: SSL/TLS connection with api.m, OPTIONS < Access-Control-Allow-Origin: * < Access-Control-Max-Age: 600 < Cache-Control: no-store < Content-Type: application/json < Date: Fri, post, size * nmemb); return size * nmemb; } output * STATE: INIT => CONNECT handle 0xaf50b0; line 1796 (connection #-5000) * Added connection, size_t nmemb, size_t size, user.c_str()); curl_easy_setopt(curl, void* userp) { ((std::string*)userp)->append((char*)contents, writer); curl_easy_setopt(curl

Mastering Development

React and Node application not uploading Images to Cloudinary, 404 error with no explanation

Post author By Full Stack
Post date December 12, 2020
No Comments on React and Node application not uploading Images to Cloudinary, 404 error with no explanation

I am trying to upload an image to cloudinary. I am using this resource as my tutorial… I am able to render a preview of the image onto my screen and I console log the base64 encoded url, and it works as it is supposed to. After I select my Image, I hit upload and […]

Tags '*'); // enables all the methods to take place return next(); }); app.use(logger('dev')); app.use('/uploads', 'desc') .max_results(30) .execute(); const publicIds = resources.map((file) => file.public_id); res.send(publicIds); }); ro, 'public'))); app.get('/*', 'true'); res.header('Access-Control-Allow-Methods', 'userinfo check') const [user, 'X-Requested-With'], ".nav", "*"); res.header("Access-Control-Allow-Headers", "author": "", "body-parser": "^1.19.0", "cloudinary": "^1.23.0", "config": "^3.3.2", "cookie-parser": "^1.4.5", "cors": "^2.8.5", "debug": "^4.3.1", "dependencies": { "bcrypt": "^5.0.0", "dotenv": "^8.2.0", "express": "^4.17.1", "http-errors": "^1.8.0", "jade": "~1.11.0", "joi": "^17.2.1", "jsonwebtoken": "^8.5.1", "license": "ISC", "main": "index.js", "mongoose": "^5.10.15", "morgan": "^1.10.0", "multer": "^1.4.2", "nodemon": "^2.0.6", "proxy": "http://localhost:3001/", "scripts": { "start": "nodemon index2.js", "test": "echo \"Error: no test specified\" && exit 1" }, "uuid": "^8.3.1" } }, "version": "1.0.0", () => { console.log(`Server started on port: ${port}`); }) here is my image.jsx(component) code import React, (req, { method: 'POST', { upload_preset: 'dev_setups', { useState } from 'react'; import Alert from './Alert.js' export default function Upload() { const [fileInputState, {path: '/'}); } const setCookieApp = (jwt) => { // let d = new Date(); setCookie(cookieName, {useState} from 'react'; import {Navbar, }); console.log(uploadResponse); res.json({ msg: 'yaya' }); } catch (err) { console.error(err); res.status(500).jso, }); module.exports = { cloudinary }; Here is my App.js file : import React, }); setFileInputState(''); setPreviewSource(''); setSuccessMsg('Image uploaded successfully'); }, //['Content-Type', Accept'); res.header('Access-Control-Allow-Credentials', and it works as it is supposed to. After I select my Image, api_key: process.env.CLOUDINARY_API_KEY, api_secret: process.env.CLOUDINARY_API_SECRET, async (req, auth); app.use('/api/friends', body: JSON.stringify({ data: base64EncodedImage }), but there is no information as to why it is happening. There is no BAD REQUEST under the NETWORK tab of my dev console. No image is ever rend, description, express.static('uploads')); app.use(bodyParser.json({limit: '50mb'})); app.use(bodyParser.urlencoded({limit: '50mb', extended: true})); app.use(cookieParser()); app.use(express.static(path.join(__dirname, form, FormControl} from 'react-bootstrap'; import Button from '@material-ui/core/Button'; import 'bootstrap/dist/css/bootstrap.min.css'; import {Ro, friends); app.use('api/upload', headers: { "Content-Type": "application/json" }, here is my index.js code const connectDB = require('./startup/db'); const express = require('express'); const app = express(); const users =, I am trying to upload an image to cloudinary. I am using this resource as my tutorial... I am able to render a preview of the image onto my, I hit upload and i get a 404 error on my POST request, image) app.use((req, jwt) }; return ( <Navbar bg="light" expan, kittys); app.use('/api/auth', NavDropdown, next) => { res.setHeader('Access-Control-Allow-Origin', Origin, removeCookie] = useCookies([cookieName]); const history = useHistory(); let userInfo = false; function isEmpty(obj) {, res) => { const { resources } = await cloudinary.search .expression('folder:dev_setups') .sort_by('public_id', res) => { try { const fileStr = req.body.data; const uploadResponse = await cloudinary.uploader.upload(fileStr, res); }); }, res)=>{ res.sendfile(path.join(__dirname='/public')); }) const port = process.env.PORT || 5000; app.listen(port, Router, send user to landing page. history.push("/"); console.log(cookies) } } console.log(userInfo, setCookie, setErrMsg] = useState(''); const handleFileInputChange = (e) => { const file = e.target.files[0]; previewFile(file);, setFileInputState] = useState(''); const [previewSource, setPreviewSource] = useState(''); const [selectedFile, setSelectedFile] = useState(); const [successMsg, setSuccessMsg] = useState(''); const [errMsg, setUser] = useState(userInfo); const handleLogin = e => { e.preventDefault(); try { userInfo = cookies.stray, useHistory} from "react-router-dom"; import {useCookies} from 'react-cookie'; import './App.css'; import LandingPage from './components/profi, userInfo will hold the // false value. userInfo = cookies.straytracker; } catch { //if token is n, users); app.use('/api/kittys'

Mastering Development

No Access-Control-Allow-Origin after many calls edit > Axios network error catch

Post author By Full Stack
Post date December 10, 2020
No Comments on No Access-Control-Allow-Origin after many calls edit > Axios network error catch

I’ve googled this issue very often and I think I’ve inserted them all which I know is redundant but I’m desperate. In my server I’ve added: app.use(cors()) and app.use(function (req, res, next) { res.setHeader(‘Access-Control-Allow-Origin’, ‘*’); res.setHeader(‘Access-Control-Allow-Headers’, ‘Origin, X-Requested-With, Content-Type, Accept’); res.setHeader(‘Access-Control-Allow-Methods’, ‘POST, GET, PATCH, DELETE, OPTIONS’); next(); }); and in the route, I’ve added: router.use([‘/api/’, […]

Tags '*'); res.setHeader('Access-Control-Allow-Headers', '*'); res.setHeader('Access-Control-Allow-Methods', '/api/:page?'], 'Access-Control-Allow-Origin': '*', 'GET, 'PUT', 'X-Requested-With'], "*"); res.setHeader( "Access-Control-Allow-Headers", "Access-Control-Allow-Method": 'GET, (req, }) .then((res) => { console.log(res.data); }) I'm not sure if cors is the issue as the route works fine, //['Content-Type', Accept, Accept'); res.setHeader('Access-Control-Allow-Methods', Accept"; return 200; } The frontend call: return axios.post("https://example.com/api/", but after a few requests I get this error and it sticks until I restart the server. 123.ngrok.io/:1 Access to XMLHttpRequest at 'https://exa, content-type'); res.setHeader('Access-Control-Allow-Credentials', data); }, DELETE, HEAD"; add_header "Access-Control-Allow-Headers" "Authorization, headers: { 'Content-Type': 'multipart/form-data', I've added: router.use(['/api/', I've googled this issue very often and I think I've inserted them all which I know is redundant but I'm desperate. In my server I've added:, it won't go away until a restart. Thank you in advance!, next) => { res.setHeader('Access-Control-Allow-Origin', OPTIONS, OPTIONS'); next(); }); and in the route, Origin, PATCH, post, res) { res.setHeader("Access-Control-Allow-Origin", res); }); }, the route works fine but after that error appears, true); //code and stuff }) In Nginx I've added: if ($request_method ~* "(GET|POST)") { add_header "Access-Control-Allow-Origin"

Mastering Development System & Network

Nginx reverse proxy and a URL rewrite

Post author By Server Questions
Post date December 7, 2020
No Comments on Nginx reverse proxy and a URL rewrite

I would like to rewrite the URL in a reverse proxy so that it removes the first segment but leaves any following segments intact. I need this to happen before it hits the proxy pass. Example: /admin/auth/local —-> (REWRITES TO) /auth/local /admin/auth/register ——-> (REWRITES TO) /auth/register My Location block: location /admin { #add_header Access-Control-Allow-Origin *; […]

Tags 'X-Requested-With'], //['Content-Type', Authorization'; proxy_set_header Host $host; proxy_set_header X-Real-Ip $remote_addr; proxy_set_header X-Forwarded-Fo, Cache-Control, I would like to rewrite the URL in a reverse proxy so that it removes the first segment but leaves any following segments intact. I need this, If-Modified-Since, OPTIONS'; add_header 'Access-Control-Allow-Headers' 'DNT, post, User-Agent, X-Mx-ReqToken

Mastering Development System & Network

ERR_CERT_COMMON_NAME_INVALID on chrome

Post author By Server Questions
Post date November 27, 2020
No Comments on ERR_CERT_COMMON_NAME_INVALID on chrome

When trying to login to my website on Chrome based browsers I get the error: Failed to load resource: net::ERR_CERT_COMMON_NAME_INVALID On firefox it works fine, tho. I installed certificates by certbot. My corresponding nginx settings look like: server { listen 80; server_name pvapp.umwelt-campus.de; return 302 https://$server_name$request_uri; } server{ # SSL configuration listen 443 ssl default_server; […]

Mastering Development

net::ERR_CONNECTION_REFUSED – Problem with CORS, Heroku App and NodeJS

Post author By Full Stack
Post date November 26, 2020
No Comments on net::ERR_CONNECTION_REFUSED – Problem with CORS, Heroku App and NodeJS

i’m facing a ERR_CONNECTION_REFUSED on client-side, hosted on heroku app and my node back-end server, running in my PC. i have configured CORS on server.js this way: var express = require(‘express’) var cors = require(‘cors’) var port = process.env.PORT || 5000 var app = express() app.use(cors()); app.use(express.json()) app.use(function(req, res, next) { res.header("Access-Control-Allow-Origin", "*") res.header(‘Access-Control-Allow-Methods’, ‘GET,PUT,POST,DELETE’); […]

Tags '*'); res.header('Access-Control-Allow-Methods', 'GET, 'PUT', 'X-Requested-With'], //['Content-Type', Accept") next() }) app.listen(port) i can't make a simple GET Request on client side. i've tested with axios and fetch fetch('http://m, but requested an insecure XMLHttpRequest endpoint 'http://myRemoteIp:5000/test'. This request has been blocked; the content must be served ov, DELETE'); res.header('Access-Control-Allow-Headers', firstly i got this error: Mixed Content: The page at 'https://tcchotel.herokuapp.com/' was loaded over HTTPS, hosted on heroku app and my node back-end server, i did the port forwarding and tested on i think that i need to mention, i'm facing a ERR_CONNECTION_REFUSED on client-side, it works. So i think the problem its really with the cross origin. PS: My port its open, next ) { res.header("Access-Control-Allow-Origin", Origin, post, remaining the ERR_CONNECTION_REFUSED Please tell me what i'm doing wrong, res); }); }, running in my PC. i have configured CORS on server.js this way: var express = require('express') var cors = require('cors') var port = pro, Thank you for reading until here.

Mastering Development

PHP cors error with headers from Angular call

Post author By Full Stack
Post date November 20, 2020
No Comments on PHP cors error with headers from Angular call

my endpoint has this: <?php header(‘Access-Control-Allow-Origin: *’); header("Access-Control-Allow-Credentials: true"); header(‘Access-Control-Allow-Methods: GET, PUT, POST, DELETE, OPTIONS’); header(‘Access-Control-Max-Age: 1000’); header(‘Access-Control-Allow-Headers: Accept,Origin, Content-Type, X-Auth-Token , Authorization’); … But with my Angular Call from Localhost, I get this error: Access to XMLHttpRequest at ‘https://example.com/createuser.php?api_key=123’ from origin ‘http://localhost:8100’ has been blocked by CORS policy: Response to preflight request doesn’t pass […]

Tags 'PUT', 'X-Requested-With'], //['Content-Type', Authorization'); ... But with my Angular Call from Localhost, DELETE, I get this error: Access to XMLHttpRequest at 'https://example.com/createuser.php?api_key=123' from origin 'http://localhost:8100' has been, my endpoint has this: <?php header('Access-Control-Allow-Origin: *'); header("Access-Control-Allow-Credentials: true"); header('Access-Cont, OPTIONS'); header('Access-Control-Max-Age: 1000'); header('Access-Control-Allow-Headers: Accept, Origin, post, X-Auth-Token

Mastering Development

Django + React Able to create new user in database, but token-auth returns 400 bad request

Post author By Full Stack
Post date November 19, 2020
No Comments on Django + React Able to create new user in database, but token-auth returns 400 bad request

So I have an app that I’m writing. It’s working, for the most part, so far. I only currently have a login and signup setup, with a ‘homepage’ that just has a logout button and some text on it so I can test. When I do signup, it posts the user to the database, but […]

Tags 'dnt', 'GET, 'grade_taught', 'http://localhost:3000/' ] }, 'JWT_VERIFY_EXPIRATION': False, 'PUT', 'room_number' ] class InstructorSerializerWithToken(serializers.ModelSerializer): token = serializers.SerializerMethodField, 'room_number' ] Related Views: class InstructorList(APIView): permission_classes = (permissions.AllowAny, 'x-csrftoken', 'X-Requested-With'], "*" ] JWT Auth settings: JWT_AUTH = { 'JWT_RESPONSE_PAYLOAD_HANDLER': 'diceapp.utils.my_jwt_response_handler', "Accept-Encoding", ) CORS_ALLOW_METHODS = [ 'DELETE', ) def post(self, ] CORS_ALLOW_HEADERS = [ 'accept', { method: 'POST', }, } Edit: Adding the request that causes the bad return. const handleLogin = (username, //['Authorization'], //['Content-Type', $username, Accept, blank=True, body: JSON.stringify({ username: username, but then I get this: Bad Request Image Here is my Instructor Model: class Instructor(AbstractUser): displayname = models.CharField(max, data.token); props.updateToken(data.token) }) .catch(error => console.log(error)) history.pus, displayName, email_address, for the most part, headers: { "Content-Type": "application/json" }, it posts the user to the database, None) instance = self.Meta.model(**validated_data) if password is not None: instance.set_password(password), null=True) email_address = models.EmailField(blank=True, null=True) grade_taught = models.IntegerField(default = 0) room_number = models.IntegerField(default = 0) Serializer(Instructor and, obj): jwt_payload_handler = api_settings.JWT_PAYLOAD_HANDLER jwt_encode_handler = api_settings.JWT_ENCODE_HANDLER pa, OPTIONS, Origin, PASSWORD, password: password }) }) .then(res => res.json()) .then(data => { localStorage.setItem('token, password) => { const url = 'http://127.0.0.1:8000/token-auth/' fetch(url, PATCH, post, request): serializer = serializers.InstructorSerializerWithToken(data = request.data) if serializer.is_valid():, so far. I only currently have a login and signup setup, So I have an app that I'm writing. It's working, status = status.HTTP_201_CREATED) return Response(serializer.errors, status = status.HTTP_400_BAD_REQUEST) class InstructorViewSet(viewsets.ModelViewSet): queryset = models.Instructor.objects.all() ser, User-Agent, validated_data): password = validated_data.pop('password', with a 'homepage' that just has a logout button and some text on it so I can test. When I do signup