WebSocket
模拟 1000 Normal Closure 响应
The connection has been closed cleanly, meaning the purpose for which it was established has been fulfilled. Both endpoints agree the session is complete.
查看完整参考 →1 HTTP 响应
HTTP/1.1 1000 Normal Closure Content-Type: application/json Date: Tue, 25 Feb 2026 12:00:00 GMT
2 使用 curl 测试
curl -i https://httpbin.org/status/1000
3 在您的框架中返回 1000 Normal Closure
django
from django.http import HttpResponse
def my_view(request):
return HttpResponse(status=1000) # Normal Closure
flask
from flask import Flask
app = Flask(__name__)
@app.route("/endpoint")
def my_endpoint():
return "", 1000 # Normal Closure
fastapi
from fastapi import FastAPI
from fastapi.responses import Response
app = FastAPI()
@app.get("/endpoint")
def my_endpoint():
return Response(status_code=1000) # Normal Closure
express.js
// Express.js
app.get('/endpoint', (req, res) => {
res.sendStatus(1000); // Normal Closure
});
spring boot
import org.springframework.http.ResponseEntity;
import org.springframework.web.bind.annotation.*;
@RestController
public class MyController {
@GetMapping("/endpoint")
public ResponseEntity<Void> myEndpoint() {
return ResponseEntity
.status(1000) // Normal Closure
.build();
}
}
go net/http
package main
import "net/http"
func myHandler(w http.ResponseWriter, r *http.Request) {
w.WriteHeader(1000) // Normal Closure
}
ruby on rails
class MyController < ApplicationController
def my_action
head :normal_closure
end
end
asp.net core
// ASP.NET Core Minimal API
app.MapGet("/endpoint", () =>
Results.StatusCode(1000) // Normal Closure
);