Comments (2)
Hi @iowelinux ,
fasthttp API doesn't provide Path().String()
because it cannot be implemented reliably without memory allocation. There is a hack, which allows converting []byte
to string
without memory allocation, but it may break in new go versions, so fasthttp API doesn't use it. So just use string(URI().Path())
if you cannot use []byte
result. This will allocate memory for string
and copy []byte
contents into string
. Or use the aforementioned hack on your own risk :)
Update:
Go doesn't allocate memory and do not copy []byte
contents to string
in the following cases:
path := ctx.Path()
// 1. string() is cheap in comparisons
if string(path) == "/foo/bar" {
doSomething()
}
// 2. string() is cheap in select
select string(path) {
case "/foo":
case "/bar":
}
// 3. string() is cheap when used as map key
m := make(map[string]struct{})
m[string(path)] = struct{}{}
_, ok := m[string(path)]
from fasthttp.
@iowelinux , see the update for string
conversion exceptions.
from fasthttp.
Related Issues (20)
- Code Leaks Memory on FreeBSD, but not on Linux HOT 4
- [Question]How to get the final real url after redirecting using DoRedirects?
- Path Traversal Attacks on Windows HOT 7
- HEAD request hangs HOT 2
- Panic when sending a lot of requests
- Fasthttp panics HOT 4
- Accessing some context in a `RoundTripper` HOT 2
- Ignoring Requests with Long URI HOT 2
- question: Add user level value to connection? HOT 1
- FastHTTP doesn't validate HTTP versions HOT 2
- application/octet-stream header gets added by default in case of a DELETE request without body HOT 4
- question regarding header parsing HOT 1
- sse panic on fasthttphandler HOT 1
- [BUG?]: SSE Handler with Fiber web framework, any http client I have implemented cannot connect.
- Question: Add client.MaxResponseBody*Read*Size? HOT 2
- Bug: fasthttp client connect to Vite dev server on localhost, tcp4 127.0.0.1:5173: connect: connection refused HOT 2
- Support for Prometheus HOT 1
- CloseOnShutdown dont work? HOT 3
- how can i use fasthttp bare minimum "net" library only without routing through the http overhead? just pure tcp rpc stuff will do HOT 1
- What is a correct way to create a proper fasthttp.RequestCtx in the unit tests? HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from fasthttp.