Known Limitations
This page lists behavior limits and defects confirmed against the current source (v0.1.2), with workarounds where available.
Parsing
| Limitation | Impact | Workaround |
|---|---|---|
A request not ended by a standalone ### (a following ### Name does not count) and with no body |
Dropped when the next request line appears; it never shows in the list (internal/parser/parser.go:69) |
End every request with a standalone ### line |
No variables (@name = value, {{name}}) or environment files |
Variables are sent literally; @ lines may end up in the body |
Write the actual values |
A trailing HTTP/1.1 on the request line becomes part of the URL |
The URL is sent with a space and the version string | Write only METHOD URL |
| Methods must be uppercase | get https://... is not recognized as a request line |
Use uppercase methods |
Headers are stored in a map |
Display order is not stable; only the last of duplicate headers is kept | Combine multiple values into one comma-separated line |
Transport
| Limitation | Impact |
|---|---|
| Timeout is fixed at 120 seconds and covers reading the body | SSE streams or long downloads beyond 120 seconds are cut off |
Regular responses are read fully with io.ReadAll |
Large responses are loaded entirely into memory |
SSE Events is the line count divided by 2 |
The count diverges from the real event count for multi-line events |
File Watching
| Limitation | Impact | Workaround |
|---|---|---|
Only fsnotify.Write/fsnotify.Create events are handled |
Editors that save via rename lose the watch after the first save | Configure the editor to overwrite in place, or restart gorc |
| Cursor is restored by index | Adding or removing requests above the current one points the cursor at a different request | Check the selected item after a reload |
| The program does not exit when watcher creation fails | The following watcher.Add runs on a nil watcher and startup fails |
Make sure system file-watch resources (e.g. the inotify limit) are sufficient |