uNetworking / uNetworking/uWebSockets

Domain and add serverName to work without ssl?

Open
#1,909 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

low priority
Dominant language
C++
Stars
19k
Forks
1.9k
Avg merge
3h 24m
Merged PRs (30d)
5

Description

Why it doesn't work like that for non ssl connections. I mean TemplateApp has this api and does nothing.

app
.domain("api.*")
.get("/users", getUsers)
.post("/users", createUser)

.domain("admin.*")
.get("/dashboard", adminDashboard)
.get("/stats", adminStats)

This could actually help me, as I'm running multi domain server with different behaviors based on domain.

Edit: From software design perspective this method should not be available in non-SSL api if it does nothing.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the TemplateApp domain API and trace the non-SSL request-routing path, focusing on how domain patterns and server names are handled. Confirm the intended behavior for the example routes and determine how completion can be verified for multi-domain, non-SSL servers.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
api, backend, networking
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.